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 user-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/user-spec-planning)<a href="https://agentmods.dev/skills/stepanenkoviktor0110-boop/ai-dev-methodology/user-spec-planning"><img src="https://agentmods.dev/badge/skills/stepanenkoviktor0110-boop/ai-dev-methodology/user-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/user-spec-planning"><img src="https://agentmods.dev/badge/skills/stepanenkoviktor0110-boop/ai-dev-methodology/user-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.00110 | $0.03537 |
| Opus 5 | $0.00055 | $0.01768 |
| Sonnet 5 | $0.00022 | $0.00707 |
| Haiku 4.5 | $0.00011 | $0.00354 |
Grade A, and why
user-spec-planning scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. Cover deploy + manual actions: what manual steps needed (API keys, bot creation, service setup)? Deploy approach (CI/CD, manual)? Post-deploy verification (MCP, curl, manual)? Pre-deploy checks (local API calls, local 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 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.
- 8d ago First seen · 165 lines · 110 tokens per session scan A 27abea996dff
user-spec-planning is a skill published in the GitHub repository stepanenkoviktor0110-boop/ai-dev-methodology (2 stars, last pushed 17d ago), with no licence file. It adds 110 tokens to every session and 3,537 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
doc-layer-system
A seven-layer documentation system for keeping product rules, interface details, data storage, implementation guidance, and tests aligned.
goal-charter
An execution charter for autonomous work after a specification has been frozen, defining the goal, boundaries, checks, recovery actions, and startup settings.
lightweight-design
A lightweight design-planning skill for resolving high-risk decisions before a coding task begins. It records the facts, affected areas, chosen decisions, and how those decisions map to requirements and acceptance checks.
code-to-7layer
A planning tool that scans an existing codebase and creates a central plan for rebuilding its documentation in seven layers. It treats code as evidence about the current system, not as the final authority.
codex-review
A manually triggered review procedure that checks completed code against a frozen specification, decision record, and project rules.
legacy-archaeology
A one-time investigation method for turning an old, opaque codebase into a searchable knowledge base about business rules, stored data, and interfaces.