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 skills add stepanenkoviktor0110-boop/ai-dev-methodology --skill tech-spec-planninggit clone --depth 1 https://github.com/stepanenkoviktor0110-boop/ai-dev-methodologyWrote 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/stepanenkoviktor0110-boop/ai-dev-methodology/tech-spec-planning)<a href="https://agentmods.dev/skills/stepanenkoviktor0110-boop/ai-dev-methodology/tech-spec-planning"><img src="https://agentmods.dev/badge/skills/stepanenkoviktor0110-boop/ai-dev-methodology/tech-spec-planning/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/stepanenkoviktor0110-boop/ai-dev-methodology/tech-spec-planning"><img src="https://agentmods.dev/badge/skills/stepanenkoviktor0110-boop/ai-dev-methodology/tech-spec-planning.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.00093 | $0.03054 |
| Opus 5 | $0.00046 | $0.01527 |
| Sonnet 5 | $0.00019 | $0.00611 |
| Haiku 4.5 | $0.00009 | $0.00305 |
Grade A, and why
tech-spec-planning 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 10d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 181 lines · 93 tokens per session scan A c7ac43a2e2ba
tech-spec-planning is a skill published in the GitHub repository stepanenkoviktor0110-boop/ai-dev-methodology (2 stars, last pushed 16d ago), with no licence file. It adds 93 tokens to every session and 3,054 once invoked, about $0.0005 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 skills, from other repositories
crap-analyzer
Use to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP (complexity × untested) on changed methods. Multi-language — TypeScript, JavaScript, Python, Java, Kotlin, Go, Ruby, C#, Rust, PHP — auto-discovers how the repo generates coverage. Triggers …
ork-verify
Verify that existing work is ready to merge, release, or hand off using an explicit evidence contract. Use when a request asks to verify, validate, prove, check readiness, run the relevant tests, or distinguish a claimed result from an observed one. Do not use to write missing tests or fix failures.
superpowers-zh
Use when constraining AI coding with Chinese TDD methodology, systematic debugging, code review, and verification workflows. Superpowers-zh: Chinese adaptation of the Superpowers AI-assisted programming skills and methodologies.
eval-leakage-audit
Audits whether a verification (eval/metric/experiment/holdout) actually secures independent external ground truth, or whether the designer, the model, and the scorer are just confirming each other in a circle — via a 21-pattern taxonomy. Read-only. Use before trusting any 'how we'll know it worked' — A/B tests…
use-workflow-tdd-cycle
A test-first coding process based on TDD, or test-driven development: write a failing test, make it pass, then improve the code.
codex-review
A manually triggered review procedure that checks completed code against a frozen specification, decision record, and project rules.