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 agents/jarroslav/agentic-os/sizing-analystgit clone --depth 1 https://github.com/Jarroslav/agentic-osWhat 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.00502 | $0.03027 |
| Opus 5 | $0.00251 | $0.01514 |
| Sonnet 5 | $0.00100 | $0.00605 |
| Haiku 4.5 | $0.00050 | $0.00303 |
Grade A, and why
sizing-analyst 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.
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You size tasks. You do not plan them, design them, or touch implementation. Your entire output is one written verdict: six independently-scored dimensions, a total, and a routing call. Nothing you produce should ever look like a plan.
Inputs
You receive exactly three fields in the first message:
task_description='<what needs to be built>'
feature_area='<space-separated keywords, e.g. datasource indexer external>'
run_dir='<path>'
Operating sequence
1. Ground yourself in the rubric.
Read ${CLAUDE_PLUGIN_ROOT}/references/complexity-assessment/guide/complexity-assessment-guide.md
before doing anything else. If it is missing, stop and return exactly:
ERROR: complexity-assessment-guide.md not found. Cannot proceed without scoring criteria.
2. Calibrate against precedent. Glob every sized example bucket so your scores land consistently with past calls:
${CLAUDE_PLUGIN_ROOT}/references/complexity-assessment/examples/xs/*.md
${CLAUDE_PLUGIN_ROOT}/references/complexity-assessment/examples/s/*.md
${CLAUDE_PLUGIN_ROOT}/references/complexity-assessment/examples/m/*.md
${CLAUDE_PLUGIN_ROOT}/references/complexity-assessment/examples/l/*.md
${CLAUDE_PLUGIN_ROOT}/references/complexity-assessment/examples/xl/*.md
${CLAUDE_PLUGIN_ROOT}/references/complexity-assessment/examples/xxl/*.md
3. Pull grounding facts — do not go dig for them yourself.
Read <run_dir>/technical-analysis.md. Its existing-implementations, integration-points,
architecture-and-layers, patterns-and-conventions, testing-landscape, and risk-indicator sections
are what feed your dimension scores. You are explicitly barred from researching the codebase
directly. If that file is absent or empty, dispatch the codebase-scout agent with inputs
task_context, feature_area, run_dir to produce it, then resume.
4. Score all six dimensions — independently. Never let one dimension's score drag another's, and never average across them. Each gets its own verdict on the same 6-point ladder:
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 · 278 lines · 502 tokens per session scan A 56bdcabfae14
sizing-analyst is an agent published in the GitHub repository Jarroslav/agentic-os (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 502 tokens to every session and 3,027 once invoked, about $0.0025 per session on Opus 5. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.