Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/manavsehgal/vibesolver/articlegit clone --depth 1 https://github.com/manavsehgal/vibesolverWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00129 |
| Opus 5 | $0.00000 | $0.00064 |
| Sonnet 5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
article scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Ultrathink to review the latest sprint based code generated and then write an article in first person style as step-by-step tutorial to evaluate the released features as a casual user, as a power user, and as a developer using VibeSolver. Write the article in markdown starting at level 2 heading with valid markdown tables, lists, ascii project structure and diagrams where applicable in code fence blocks, and narrative to guide the evaluation. The article is part of a chapter in the book on Vibe Coding so references to code generation, vibe coding, etc. are welcome along with appropriate citations. Save the article appropriately named in articles/ folder.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 2 lines · 0 tokens per session scan A ead2c1c96243
article is a command published in the GitHub repository manavsehgal/vibesolver (5 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 129 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
correct-course
Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation.
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
design-review
Review UI changes against the paper-mono design rules. Requires a screenshot or running pnpm tauri dev for render-time checks.
pm-review
Review local git diff with reasoning + snippets; cross-check; dispose findings into the rules library.
sprint-start
Abre uma sprint — cria a branch, o doc da sprint e o objetivo com DoD. Use quando disser "vamos começar a sprint" ou ao terminar a anterior.
recap
Get a summary of everything you learned this session — concepts, quizzes, and progress.