<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Context Window on SoloSoft</title><link>https://www.solosoft.dev/tags/context-window/</link><description>Recent content in Context Window on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 10 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/context-window/index.xml" rel="self" type="application/rss+xml"/><item><title>Installing All 17 E-Commerce Skill Repos: 1,353 Skills, 2.5 Million Tokens, and the 26 Files That Never Load</title><link>https://www.solosoft.dev/post/17-ecommerce-skill-repos-install-audit/</link><pubDate>Sat, 10 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/17-ecommerce-skill-repos-install-audit/</guid><description>&lt;p&gt;The request was straightforward: install every skill from these seventeen repositories in order, and report what each one contains.&lt;/p&gt;
&lt;p&gt;I did it. All seventeen repositories are real, they total 855 MB, and they contain 1,353 skills that an agent can load plus 28 files that look like skills but are not. Everything is installed — 1,337 directories sitting in &lt;code&gt;~/.claude/skills/&lt;/code&gt; — and the per-repository breakdown is below.&lt;/p&gt;
&lt;p&gt;What the exercise also produced is a measurement nobody makes before recommending a skill collection: the combined markdown is 10.00 MB. In tokens, that is somewhere between 2.5 and 2.9 million — two and a half times the entire context window of the model these skills are written for. Six repositories also behave differently from their own documentation, and one of them installs nothing at all if you follow its README exactly.&lt;/p&gt;</description></item><item><title>Auditing REA: 15,095 Stars, 133 MCP Tools, and the 209,619-Token Bill for Analysing Eight Files</title><link>https://www.solosoft.dev/post/rea-mcp-reverse-engineering-audit/</link><pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/rea-mcp-reverse-engineering-audit/</guid><description>&lt;p&gt;&amp;ldquo;See a feature you like. Understand how it works, down to the binary level.&amp;rdquo; That is REA&amp;rsquo;s pitch — one MCP server for reverse engineering across binaries, applications and runtime behaviour — and 15,095 stars on &lt;code&gt;morluto/rea&lt;/code&gt; say it landed. The repository is pushed to within an hour of my writing this, ships 26 npm versions in 88 days, and runs 16 GitHub Actions workflows with names like &lt;em&gt;Real Hopper E2E&lt;/em&gt; and &lt;em&gt;Real Ghidra Windows E2E&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;So I installed &lt;code&gt;rea-agents@5.0.0&lt;/code&gt;, spoke raw JSON-RPC to its MCP server, built an eight-file Electron application as a fixture, and pointed the analyser at a 14 MB JavaScript directory to find the edge. What came back is one of the more honest tools I have audited this year, and a bill nobody quotes in the README.&lt;/p&gt;</description></item></channel></rss>