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 AndreVianna/aid-methodology --skill aid-create-backloggit clone --depth 1 https://github.com/AndreVianna/aid-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/andrevianna/aid-methodology/aid-create-backlog)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-create-backlog"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-create-backlog/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/andrevianna/aid-methodology/aid-create-backlog"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-create-backlog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00131 | $0.03219 |
| Opus 5 | $0.00066 | $0.01610 |
| Sonnet 5 | $0.00026 | $0.00644 |
| Haiku 4.5 | $0.00013 | $0.00322 |
Grade A, and why
aid-create-backlog 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 9d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Backlog (realize a seed into backlog.md)
/aid-create-backlog realizes a ready backlog seed at .aid/design/backlog.md
into the committed KB document at .aid/knowledge/backlog.md. It is a create-stage
skill under the shared contract in .claude/aid/templates/design-lifecycle.md (class 1),
consuming the seed /aid-design-backlog produces and never touching .aid/design/ for any
other purpose.
- Boundary vs
/aid-update-backlog: that skill revises existing item entries. When the item sections already carry committed content this skill routes to it rather than overwriting them. - Not a numbered pipeline phase; does not route to
/aid-execute.
State machine: INTAKE -> GUARD -> REALIZE -> REGISTER -> VERIFY -> PRESENT -> DONE.
Print the [State: NAME] -- {purpose} entry line on each state.
State: INTAKE
- Require a subject. Empty argument -> ask one bootstrapping question ("What items do
you want to accept into the backlog -- or run
/aid-design-backlogfirst?") and wait. - Allocate, exactly per
design-lifecycle.md § Skill shape -- Allocation-- the Work Initiation Gate, theninitiator: aid-create-backlog,active_skill: aid-create-backlog,pipeline.path: lite,lifecycle: Running.phaseis not driven. - Read the seed at
.aid/design/backlog.md. If no seed exists, inform the user and ask whether to proceed without one (items entered interactively) or to run/aid-design-backlogfirst; do not proceed silently. - Read the destination at
.aid/knowledge/backlog.mdif it exists. Classify its state: absent | present-sections-empty | present-sections-populated. - Read
tech-debt.mdat.aid/knowledge/tech-debt.mdif it exists. The seed may name candidate rows to promote; know their current state before the confirm gate runs. - Classify complexity (model + effort) for the
aid-architectdispatch below; verifier tier >= producer tier (agent-dispatch-tiering.md).
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.
- 9d ago First seen · 242 lines · 131 tokens per session scan A b56613b6df44
aid-create-backlog is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed 3d ago), licensed MIT. It adds 131 tokens to every session and 3,219 once invoked, about $0.0007 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.