Nate B Jones
Opus 5.5 vs The Rest: Is this the new industry standard?
Ask the tutor about this video
Sign in with a verified email and ask the tutor anything about this video.
TL;DR
Research summary
▶ Opus 5.5 and the LEGO demonstration
The speaker says Opus 5.5 makes them more willing to give Claude work because its writing is easier to steer and its three-dimensional visual work is impressive. They introduce task efficiency—how many tokens and attempts a task takes—as a key measure, then show a LEGO model based on their beanie hat logo. They describe a 514-piece build with a 63-page instruction booklet containing 58 steps, plus a model file, parts list, BrickLink wanted list, geometry check file, and LDraw file. The speaker says the files agree on the piece count and that the model aligns with the logo.
▶ Token usage, subscription value, and pricing
The speaker says the LEGO task used 89 million tokens and 1% of their weekly Claude usage. They estimate those tokens would have cost at least $44 at API pricing; they also compare the task with a $200 monthly subscription, saying the equivalent is roughly 25% of the subscription price, while the task used 1% of weekly usage. They give Opus 5.5 API rates as $4 per million input tokens and $20 per million output tokens, which they say are 20% below Opus 5 and 60% below Fable 5.1, whose stated rates are $10 per million input tokens and $50 per million output tokens. They caution that Anthropic’s claim of typical workloads costing about 40% less on Opus 5 combines lower prices with fewer tokens, so it does not mean every task uses 40% fewer tokens; input, output, cache, and context have different rates, and subscribers should also track usage. They cite GitHub and Lovable reports of fewer steps and Spotify’s report of completing the same tasks more cheaply and quickly, alongside individual user reports, as evidence consistent with efficiency gains.
▶ Measure the whole task and preserve room to iterate
The speaker says greater efficiency can leave room to revise work, but token use depends on the task: a complex scene such as a city would use more than the LEGO build. They argue that a good-looking frame or screenshot is not the whole job; measurement should cover planning, attempts, corrections, and the completed result. They describe code-based three-dimensional graphics in a browser, naming 3.js as a tool for manipulating objects, materials, lighting, and camera angles, and say Anthropic models are good at producing visual results through coding tools under direction. They contrast their positive view of Opus 5.5 with reported past difficulties in writing and instruction following, citing individual public accounts and a GitHub issue as examples, while emphasizing that these are individual accounts and that user experience matters.
▶ Writing quality and steerability
The speaker says Anthropic’s Opus 5.5 announcement identifies communication feedback about Opus 5 as an issue and names clearer writing and better adherence to writing instructions among the top fixes. In the speaker’s view, Opus 5.5 feels closer to Opus 4.6 in writing while offering more intelligence, and responds quickly to direction on complex tasks. They argue that useful AI writing preserves the author’s intent: simplifying should not remove a key complication, warming the tone should not weaken a firm decision, and increasing confidence should not erase needed uncertainty. They say polished edits can still make writing less clear or useful, and praise Opus 5.5 for being steerable, including when asked to preserve uncertainty or adjust only part of a passage. For the LEGO model, they suggest possible targeted revisions such as changing the beanie shape while keeping the glasses, slowing the assembly, adding steps, or changing bricks and instructions together. They describe code-based visual scenes as allowing targeted changes to objects and movements while continuing to develop the same scene.
▶ Overnight work needs clear boundaries
The speaker cites an announcement account from Cleo describing an engineering task across six repositories left unattended with Opus 5.5 for 18 hours. They note that such work involves autonomous decisions and that the output needs checking. Based on two or three overnight tasks they say they tried, they found long-running builds work better with clear stop conditions and a well-defined evaluation or definition of done. They say Opus 5.5 can keep going, and recommend defining the universe in which it should work to avoid unnecessary token use. For the LEGO task, they say specifying the expected piece count and complexity at the outset limited the model’s decisions and saved tokens; the desired finish was a working scene with requested changes and checks completed.
▶ AI tools inside model labs
The speaker connects task efficiency to AI tools used by labs in development. They attribute to Anthropic the statement that, as of May, Claude authored more than 80% of code being merged into its code base, and say OpenAI describes researchers using agents to write code, run experiments, and troubleshoot. They describe the relationship between user feedback and internal AI tools as a possible way to investigate and test fixes more quickly, while acknowledging that they do not have Anthropic’s full internal history of how Opus 5.5 was produced. They suggest this may help explain improvements such as writing and say their role is to report what works and the cost per task rather than pick a favorite model.
▶ Efficiency, user value, and model releases
The speaker says that if the LEGO model and files take less effort and fewer tokens, a user can either spend less or use the remaining capacity to iterate further or start another project. In their view, Opus 5.5 makes complicated tasks feel lighter and leaves more room for decisions. They connect this to how labs deliver task-efficient frontier models and respond to paying users, while noting that OpenAI and Anthropic have different model lineages and internal models. They claim the approximate interval between major model releases has shrunk to about two weeks, citing a recent figure of about 18 days, and speculate that AI tools help labs improve faster. They say a 500-piece LEGO build would have exceeded and broken their benchmark two or three months earlier, but now uses 1% of their weekly usage. They emphasize that consumers choose which models get their money and assignments, and that successful, efficient responses give labs a reason to care about how people work with their systems.
▶ How to compare models on real work
The speaker recommends measuring cost per task using the files and work a person actually handles, such as spreadsheets, documents, or a code repository. When a new model arrives, they suggest repeating a prior task with the same starting point, prompt, and setup, then tracking total tokens, estimated API cost, subscription usage, attempts, failed attempts, corrections, and how much human involvement was needed. They say the final result should meet at least the previous model’s standard and advise keeping unsuccessful results as well as successes. In their assessment, Opus 5.5 performed better than previous Opus models and better than Fable for this task because it was cheaper and faster and required less repeated explanation and guidance. They say comparison should reveal where a model improves—for example, visual work or writing—and where it may not improve as much, such as research, so users can judge how much that changes their day.
▶ Personal workflow changes and final recommendation
The speaker says Opus 5.5’s visual taste led them to assign it a complicated visual-design task with about 90-some elements; they say it completed the task from one prompt without using up their weekly budget, prompting them to change their workflow. They encourage viewers to build an assignment-testing kit tailored to their own prior usage and offer a linked prompt for doing so. Their closing recommendation is to choose a meaningful assignment, measure it consistently across model releases, and judge whether the result provides more value. They say documenting both successes and failures helps users and labs understand model performance, and invite viewers to share their views on Opus 5.5.
Full transcript
[0:30] 50 bucks a week. A task uses about 1% of my weekly allowance, a task I will show you in this video. It's a complicated one. That's 50 cents of the subscription I'm actually paying for. So, in this video, I'm going to show you the calculation, the work behind it, a sample LEGO build cuz we're going to have fun, and most importantly, I'm going to show you how to figure out whether you're getting that improvement on your own tasks. So, let's get into it and how it works. Think about what you're paying for when you use a model. There is a price for the tokens, the
[1:00] chunks of information it processes and generates. But how many times does it need to read the files to do that? How many attempts does an AI make to make a change that you care about? How many times do you have to keep explaining again and again? How many times does it churn out? All of that is part of getting the job done. So, when a model gets the job done efficiently, the price of what you're getting done can go way, way, way down. Now, I get it. This gets really squishy really fast. Your tasks are not my
[1:32] tasks. You could spend all day with exactly the same model and get a very different result because you're asking it to do different work, and models are spiky. That's what I want to get into with 5.5 in this video, how you can figure out what the efficiency gain is worth to you. So, look at this. It's my logo in LEGO. Say that five times fast. It has the beanie, it has the glasses, it has a clear column that holds up the glasses and the hat over a nice base. Now, I'm a LEGO guy and I like beanies, so of course this is what I wanted to
[2:02] make. You can watch the pieces come together in the video and then see the finished model from the front and it lines up with the logo. It's beautifully put together. And look what came with it. There's a 63-page instruction booklet with 58 different build steps. It shows which parts to add and even tells you when a piece has to attach from underneath. It gave me a model file, a parts list, and a bricklink wanted list. I can order it all. The model and the list both agree this is a 514-piece build.
[2:33] That's a lot of work. Do you want to guess how many tokens that was? It was 89 million tokens. Do you want to guess how much of my Claude usage that took up with Opus 5.5? This is all Opus 5.5. 1% of my weekly usage for that. And those 89 million tokens, they would have cost me at least $44 if I was at API pricing. I didn't have to pay that $44. And by the way, if you do the math on a $200 a month subscription, we're talking about 25% roughly of the subscription price,
[3:03] but I didn't have to pay that. And it only took 1% of my usage for a week. And for all of that value, I get multiple files. I showed you a video file. I talked about the parts. I talked about the instructions. I also got a whole check file that checks the geometric connections between bricks. And I got an LDraw file that actually makes sure that the LEGOs can connect and and and get put together. And this gets at a larger pathway that I think is under discussed
[3:33] that Anthropic is actively using when it comes to AI development. And that is using code to do visual work. So, what does all of this cost? Opus 5.5 charges $4 per million input tokens and $20 per million output tokens. Those rates are 20% below Opus 5. They're also 60% below Fable 5.1's $10 per million input tokens and $50 per million output tokens. So, we are seeing significant decreases
[4:04] for really, really solid intelligence that in many ways mirrors what Fable can do on ordinary tasks, but is much more efficient and much cheaper ultimately. And so, these are useful baseline numbers, but it's important to know how much the model chews on those tokens to actually do the job. This is where that task efficiency comes in. Now, Anthropic says, "Typical workloads cost about 40% less on Opus 5 from a combination of lower prices and of course, the model using fewer tokens to get the work
[4:35] done." So, keep that in your head, right? 40% less cost doesn't tell you that a task used 40% fewer tokens. Instead, think of it as input, output, cash, context, those all have different token rates, and ultimately, to understand the efficiency improvement, you are going to need to look at the token usage across all of those buckets, as well as the API bill, and then look, if you're a subscriber, at how that chews up your usage. But, the 40% seems plausible. Other users are pointing to this same kind of savings, the same kind
[5:07] of efficiency that I'm showing you here. In the reports Anthropic features in its announcement, GitHub and Lovable both describe Opus using fewer steps with 5.5, and Spotify describes doing the same tasks more cheaply and quickly. Uh and I see individual users reporting this all over X. And that's what makes this much more interesting than a typical model release to me. It's the idea that we can listen to our users, we can respond, we can use AI tools inside a company to build a better model that is more task efficient, and that
[5:37] delivers more value. So, think about that Lego build one more time. Claude has to work through that model, right? Claude had to work through the animation, had to work through the information in those build files, recheck everything. Every time something needs another attempt, Claude had more work to do. If it gets the design right sooner and responds more efficiently and usefully when I ask for a change, we have a lot more room to make this LEGO build better together. And that's the kind of efficiency that we're going to care about in real work. It's whether we
[6:08] can build it and then iterate it and feel like we have lots of room in the window to continue to improve together. Does that automatically mean that every single scene will use fewer tokens because we steer more cleanly? Well, it's going to depend on you, right? How complex is your scene? I saw scenes that looked very complex with the 5.5 release. I saw someone building an entire city. I think I saw Lower Manhattan made with Opus 5.5. Those look cool. They're going to use a lot more tokens than my LEGO build. But, one of
[6:39] the things I want to call out is we need to stop counting our tokens too early. If you've got a great-looking frame, if you've got a great-looking screenshot, that's wonderful. You still have work to do. And so when we talk about tasks, not just LEGOs, real work tasks, the real work needs to be the whole job and we need to measure that whole job. And that's why I did the whole job in terms of planning out the LEGO build and then I gave you the token bill for it. And that's why I'm impressed with the
[7:09] task efficiency, not because I got, you know, a particular screenshot back or because the video looked nice. So, code like 3.js lets you build three-dimensional graphics in a browser. It lets you manipulate the objects and materials and lights and have a camera angle. Uh and there are lots of different coding tools we can have for visual jobs, but I mentioned 3.js because the model, especially Anthropic models, have gotten extremely good at using coding tools like that under
[7:41] direction, under a simple prompt from you to produce beautifully tasteful results. And this is also what I love about the writing improvements in this model. Think back to Opus 4.6. It seems ages ago, right? Anthropic felt like it was at the top of their game, right? The writing was excellent, the coding was excellent. I wanted to keep using Claude all the time. And then, as we went through 4.7 and 4.8 and Fable, getting the work I wanted became more complicated. And that's not just me, by the way. I am actually reflecting back a lot of sentiment that the community fed
[8:13] back to Anthropic over the course of the last few months, particularly around writing. You can find that frustration out in public, right? Bram Cohen wrote about Claude's argumentative behavior very publicly in a memorable article entitled Why Is Claude Turning Into an And you can even find this in Anthropic's GitHub issue tracker, where a user described writing instructions being acknowledged and then ignored. And look, these are individual accounts that I'm sharing, but you can start to see a pattern when you see enough of these.
[8:44] And I've seen them all over the web. And what really matters is your experience, right? It's your and my experience. You can recognize when a model gives you what you ask for the first time, when it gives you exactly what you need, when it's steerable, when it doesn't fight back. And of course, Anthropic has a lot riding on getting that experience right. The company's growing rapidly. They're reportedly pursuing an IPO. People still have to choose Claude for their work. If the model makes you spend your afternoon correcting it, that experience is going to affect what you choose to open
[9:14] tomorrow. And Anthropic has acknowledged the issues, right? Anthropic says it listens. Specifically, the 5.5 announcement names communication feedback about Opus 5 as a big issue that they were working to fix, and describes clearer writing and better adherence to writing instructions as one of the top fixes in 5.5. So, for me, 5.5 feels so so much closer to what I loved about 4.6, but of course with so much more intelligence behind it. I can give it direction and get somewhere with the
[9:45] writing really quickly. I can give it direction like I did for Lego and get somewhere really quickly, really efficiently on complex tasks that of course I could never attempt with 4.6. And when we talk about writing, I think we often assume that all AI writing is AI slop. That's not true. Good AI writing preserves your intent. A good revision has to preserve your intent. Suppose you ask for a paragraph to be simpler. The model can make it shorter by removing the complication that made your argument worth reading and then you have to fight with it to put it back. Or
[10:16] it can make the tone warmer by softening a decision you wanted to state firmly. It can make a sentence more confident than you meant by erasing uncertainty that you know you needed to communicate. Those edits can sound polished while making the writing less clear and useful. And this is exactly the line between AI slop and useful writing. And this is why I've often advocated for the difference around writing to be defined by the quality of what you make,
[10:47] not by how you made it. Because in the end, it's either communicated clearly or it's not. And this tool, Opus 5.5, definitely makes it easier to communicate clearly. And this is also why I care so much about steerability and it's one of the things I loved about 5.5. If I want to say, "Hey, keep this, keep the uncertainty, make this part easier to understand." I can just talk into the model and when the correction comes back right away, I don't have to redo it, right? And I found that Opus 5.5 is very steerable in that regard.
[11:17] Think about a revision to the Lego logo that I showed earlier in this video. Suppose I wanted the beanie to be like a tall hat, but I want to keep the glasses exactly as they are. Or I want the assembly to slow down so I can follow it. I want more steps. Those are specific changes. Uh I can change the bricks. I can change the parts list and the instructions to agree with how I want it to look. Maybe I want it to look smoother. I want to make sure that when I give those decisions, every single revision
[11:47] across a complicated 500-piece build reflects my intent. And this is where Claude's visual work gets super interesting. With a scene built from code, it's possible for Claude to go in and specifically change the relevant objects and movements surgically. So, the coding ability of Claude becomes a way to visualize and make the image and animate it and revise it cleanly, and I think that's really special. You can have a conversation about the camera or the shape of the hat and keep developing the same scene together as you figure out what you
[12:18] want. Now, what about overnight jobs? How does this model do? How does Opus 5.5 do on jobs that run overnight? In Anthropic's announcement, Shawn Hanse at Cleo describes leaving Opus 5.5 with an engineering task across six repos unattended for 18 hours. These are things we've heard before, right? And that's a lot of room to get work done. It's also a lot of decisions that the model needs to make autonomously while you're off sleeping, right? Doing something else. And in that world, it's
[12:48] really important for us to come back and make sure that we have good working code. And so far what I've found, and I've done overnight tasks with Opus 5.5 as well. Uh so, this is not just me relying on others. I did two or three overnight tasks as I was testing it early on. What I found was Opus 5.5 does better with those long-running builds when you give it clear stop conditions and a very clear and determined eval or definition of done at the end. The more
[13:19] you're clear about that with a long-running assignment, the better off you are. And that's not a particularly new or even particularly special to 5.5 insight, but I did find it was important to ensure that the the passion that Opus 5.5 seems to bring to a problem doesn't just lead to a really long-running job without a determined stop condition. And so, the lesson I've taken from 5.5 is that it's important to define the universe you want the model to work in. This thing just loves to go and go and go, right? And I love that persistence,
[13:49] and I wanted to attach to the job I gave it so I don't chew tokens unnecessarily. It comes back to efficiency. And so, with a package like this, with the logo LEGO that I built, what I wanted to do was give it a definition of done. And that's why I specified at the top how many pieces, the complexity that this would have to be so that it did not have to do that itself. And that saved me a bunch of tokens. It it enabled the model to not have to model the entire world of my logo hat and arbitrarily decide and
[14:20] then decide it wasn't doing good enough and then push itself harder. These models push themselves. And so, it's up to us to give them a world that they can operate within and be efficient. And then when we're finished, we're finished. The scene works, the changes are there, we've checked the things that need to be checked, the LEGO logo works, right? And I want to connect that to the bigger story because the labs are getting better tools for doing this work as well. And some of those tools are their own AI models, ones you and I haven't seen. We tend to talk about a
[14:50] release as though it came out of nowhere. Here's the model, here's the score, where does it rank? Meanwhile, Anthropic says that as of May, Claude has authored more than 80% of the code being merged into its code base. That matters, right? 80%. So, that's AI helping to design AI, right? It's And we talk about this as recursive self-improvement. We talk about this as AI-assisted research. There's different words, but it tells you how much the work inside the company is starting to
[15:20] change. OpenAI describes researchers using agents to write code, run experiments, and troubleshoot problems. That is a lot that the labs are using AI on to design AI. And this is going to matter, and it's going to help us understand why Opus 5.5 is the way it is. And this matters because the way that we are using AI is actually shaping AI tools like Opus 5.5 that the consumer sees in ways that make it easier for us to use those models. We often think of
[15:50] AI as being less responsive to consumers, but in this case, it's kind of the opposite, and I want to tell that story. We don't have the full internal history of how Anthropic produced 5.5. But what I think is encouraging is the possibility that connecting these dots opens up. Think about it this way. Users like you and me can point out something that makes a model difficult to work with. And the people fixing it have increasingly capable AI tools helping them investigate and test changes
[16:20] rapidly. And that can shorten the wait for really useful improvements. And with 5.5, I can see strides in things like hear about every day, like writing. And I want to look at what those strides let us do. People ask me, "Nate, don't you have a favorite model?" And I say, "I use the models that work, right? I don't pick favorites." Uh and so my job is just to report on what's working, report on cost per task, and be glad that we are living in a world where we have so much intelligence. Here's the part that gets me excited ultimately. Suppose I can get this LEGO model and the build
[16:50] files working with much less effort and fewer tokens as I've been describing. I could stop there, and I could spend less. Or I could go farther and build something else. Maybe I work on the animation, maybe I want a bigger LEGO build. Uh maybe I want to go beyond LEGOs and don't do real work as I as I've been describing. I actually do do real work, not just LEGOs. But ultimately, because it's task efficient, Opus 5.5 leaves me more room to make the decisions that matter, to iterate and then to pick up another project. And
[17:21] when I do that work, it becomes something that makes me feel like the load is lighter on complicated tasks. And that gets at why we use frontier intelligence in the first place. And that is going to be the larger story as we look into the IPOs for both Open AI and Anthropic is ultimately how are they delivering extraordinary frontier value that is task efficient and how are they listening to their paying users and responding in real time. The larger story of Opus 5.5 is that all of that
[17:53] came together in this release and you can see the Anthropic team responding to user feedback. You can see the model coming out and being task efficient and you can see how that pays off in terms of what users can use. Now, every lab has their own journey to go in here. Open AI and Anthropic are in different places. I'm not saying their internal models are nearly the same. They're obviously different. They have different model lineages. It's part of what makes it great as a consumer. Where we are right now is we are living in a world where AI is
[18:24] helping AI development make a real difference for consumers. We have shrunk the approximate number of days between major model releases to about 2 weeks. I think the number I saw recently was about 18 days. Part of how we have gotten that fast and part of how we have gotten a chance to have that much responsiveness to what we need as frontier intelligence users is because the labs have AI tools to help them get better. And so when I look at the
[18:54] future, I'm optimistic. I am hopeful because I'm looking at this and I'm saying, "Wow, what is Anthropic got cooking next? What is Open AI got cooking next?" I bet it's pretty cool. And so here's where we are. We have a model that is good enough in 2026 that I can do that 500 piece Lego build that I showed you, which would have maxed out and broken my Lego benchmark just 3 months ago or 2 months ago. And it only uses 1% of my weekly
[19:25] usage. That's where we are. I can't wait to see where we get in 2 or 3 months. It's going to be so cool. And this is why I think our experience as consumers matters to the larger story. This is why I started with what I actually built with Opus. I wanted to share it. I want you to share it with me. We all have work we need to do. We know which decisions we want preserved. We can explain where the result fell short. We also choose which models get our money, which models get the next assignment. When a model helps us finish efficiently and responds really well to
[19:55] direction, we have a good reason to keep using it. And those choices give the labs a reason to care about the details of working with their systems. Ergonomics of frontier models matter a lot. They matter a ton. And so you might be wondering, "How do I get a useful answer, Nate? How do I find out what my cost per task is? And is Opus helpful to me? How do I know? The with the work I actually do, not with the Legos, with the materials I've got." So, for this one, here's what I would do. I would
[20:25] take the files that you are usually working on. Maybe it's spreadsheets for you. Maybe it's docs for you. Maybe it's a code repo. But whatever it is, run it again. Run a task you ran before when a new model arrives. Try and use the same starting point, use the same prompt, and give the new model the exact same setup the old one already built. And then let it run and see what it does. And make sure you track it just as I tracked the total tokens. And I did a approximate
[20:55] bill count against API costs. And I also measured the weekly usage slice. Do that, right? Test it and see. And then benchmark it against previous models. And and the more you are able to understand the full scope of the task, the attempts that failed, the corrections, the work that happened along the way, how much you had to get involved. One of the things I loved about the LEGO builds is I barely had to get involved at all. Like it was beautiful. It just got done. I got other things done in the meantime. The
[21:25] ultimate result has to meet at least the same standard as your previous model. And the reason I'm talking about Opus 5.5 is it did a lot better than previous Opus models at this. It did better, in my view, than Fable cuz it was so much cheaper and faster. And so I didn't have to keep explaining the same things over and over again. I didn't have to pay as much in terms of weekly usage. It was cheaper to do. It was less guidance. It just it made a lot of sense. And so when you were doing this cost per task work, don't just keep the successes. Keep the moments where you
[21:56] were like, oh, this model didn't do it for me, right? It didn't work for me. This release didn't work for me. The more we're able to document that, it tells all of us what we need to know to actually make use of AI, right? Cuz what we ultimately care about is how often something is usable. How often something is spent across attempts. And then at that point, you can start seeing where the improvement lies. Maybe visual work gets dramatically better and writing improves, uh, and maybe the research side isn't there as much. How much of
[22:28] your day changes on that? And that's going to determine what this release is worth to you. Let me give you an example from my experience. When I used Opus 5.5 and I saw the visual taste that the model had, I actually switched where I was going for visual taste and design work on a project I'm working on and I gave it to Opus 5.5 because I liked how Opus 5.5 handled the visuals and I trusted that a complicated, it was like 90-some element
[22:58] visual design job was something that I could hand with one prompt to Opus 5.5 and I and I knew it would get it done and it did and it did not chew up my weekly budget. And so, I basically reasoned from what I could learn and test and changed where my workflow went as a result. I'm doing that all the time. And so, for you, my challenge to you is make sure you build a real assignment testing kit for models. If you haven't done that, yes, of course, I
[23:28] can help you with that. I have a whole prompt to work with your model to look at your previous usage patterns and to come up with a realistic just for you prompt that is not a Lego bench, right? That is not whatever Nate's design files were. It is for you. And so, with that, if that's something you're interested in, I'll put the link, you can go get it. That's fine. But ultimately, I want you to see the larger story here. We are in a world where we can give feedback to the labs, they can respond, we can see better models coming out, and we can get
[24:00] more done. And the only way we know if that works for us is if we are actually tracking our tasks and making sure that those tasks actually get more value back. So, pick something where you're going to care if the result is good, measure it, and come back and measure it again. Make sure that you test it consistently across model releases. That's how you get excited. That's how you know when a breakthrough has happened. That is my take on Opus 5.5. I'd be curious for your take on Opus 5.5. Let me know in the comments.