Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/huuanh20/awesome-ai-agent-skillsnpx agentmods add skills/huuanh20/awesome-ai-agent-skills/sr-planWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/huuanh20/awesome-ai-agent-skills/sr-plan)<a href="https://agentmods.dev/skills/huuanh20/awesome-ai-agent-skills/sr-plan"><img src="https://agentmods.dev/badge/skills/huuanh20/awesome-ai-agent-skills/sr-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/huuanh20/awesome-ai-agent-skills/sr-plan"><img src="https://agentmods.dev/badge/skills/huuanh20/awesome-ai-agent-skills/sr-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00052 | $0.01150 |
| Opus 5.5 | $0.00021 | $0.00460 |
| Sonnet 5.5 | $0.00010 | $0.00230 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
sr:plan 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 1mo 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sr:plan
Goal: produce 12 plan files — one per SRS section — that serve as unambiguous blueprints for SRS generation. No summarizing, no truncation.
Step 0 — Identify Project
AskUserQuestion: "Which project to plan? (slug)"
Read projects/{slug}/spec.md. If missing, tell user to run /sr:spec first.
Load .claude/skills/srs-workflow/references/plan-structure-guide.md.
Step 1 — Write Plan Files
Create all files under projects/{slug}/plan/. For each file, follow the detailed
spec in plan-structure-guide.md for what must be included.
Write in this order (each file before proceeding to next):
00-overview.md— master map, FR/NFR count totals, actor table, assumptions01-introduction.md— §1.1 Purpose, §1.2 Scope (IN/OUT table), §1.3 Definitions, §1.4 References, §1.5 Overview02-overall-description.md— §2.1 Perspective, §2.2 Functions, §2.3 User Characteristics, §2.4 Constraints, §2.5 Assumptions, §2.6 Apportioning03-01-external-interfaces.md— UI screens, hardware, software APIs, communication protocols03-02-functional-requirements.md— ALL FRs with "shall" stubs + GWT stubs + priority03-03-performance.md— ALL NFRs with numeric Response Measure or [TBD]03-04-database.md— entities, retention, volumes, PII fields03-05-design-constraints.md— imposed tech stack, compliance-driven constraints03-06-system-attributes.md— reliability, availability, security, maintainability, portability, usability03-07-other-requirements.md— i18n, legal, operational, transition, trainingappendix-a-glossary.md— all domain terms needing precise definitionsappendix-b-open-issues.md— every [NEEDS USER INPUT] from all plan files, with owner + resolve-by
FR numbering rules (enforced across all plan files):
- Sequential: FR-01, FR-02, FR-03 … no resets between sections
- Format:
FR-NN [Essential|Conditional|Optional] - Every FR must have: Requirement (shall clause) + Given/When/Then stubs
- Tag unclear items:
[NEEDS USER INPUT: {specific question}]
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.
- 1mo ago First seen · 117 lines · 52 tokens per session scan A adc31733346a
sr:plan is a skill published in the GitHub repository huuanh20/awesome-ai-agent-skills (1 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 1,150 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
loop
Work through the taskboard unattended for hours, pacing against the usage limits and filling the gap before a reset with CPU-only jobs. Use when asked to run all day, work unattended, or loop over tickets.
learn
Record a correction, decision, finding or failed attempt in the wiki. Use when the user corrects you, when a decision is made with a reason, when an experiment returns a verdict, or when you learn something the next session would otherwise re-derive.
wrap-up
Close out a task by folding what it taught into the wiki, updating the taskboard, and linting. Use at the end of a task, before clearing a session, or when asked to wrap up.
handoff
Write one self-contained goal that a fresh session can continue from. Use when context is running out, before clearing a session, when usage passes 95% on a long run, or when asked for a handoff.
init
Set up Dory in this repo by exploring it, creating wiki/ from the template, and connecting the usage statusline. Use when a project has no wiki/ yet, or when asked to set up Dory.
check-mcp-json
Safely review, triage, repair, and merge ToolSDK MCP Registry package JSON pull requests. Use when an agent needs to validate files under packages/, detect duplicate registry keys, classify community PRs, make authorized fixes on contributor branches, close invalid or duplicate PRs, or squash-merge approved PRs.