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-deploygit 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-deploy)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-deploy"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-deploy/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-deploy"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-deploy.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.02620 |
| Opus 5 | $0.00026 | $0.01310 |
| Sonnet 5 | $0.00010 | $0.00524 |
| Haiku 4.5 | $0.00005 | $0.00262 |
Grade A, and why
aid-deploy 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Package & Ship
State machine: IDLE → SELECTING → VERIFYING → PACKAGING → DONE.
Package completed deliveries into a release.
Agents Involved
- Default executor:
aid-operator(orchestrates the release: verifies build, packages artifacts, updates statuses). - Specialist consults (optional):
aid-tech-writerfor release notes / changelog,aid-operatorif CI/CD configuration changes are needed during release,aid-reviewerfor final pre-release verification.
Argument-Hint
/aid-deploy work-NNN
/aid-deploy "<free-form description of what to ship>"
Two invocation modes (invocation-context detection; see ## ⚠️ Pre-flight Checks
Step 0):
work-NNNpresent -- the existing pipeline path below runs unchanged (IDLE -> SELECTING -> VERIFYING -> PACKAGING -> DONE, post-Execute). Required: work ID. If only one work exists, auto-select it.- No
work-NNN, a free-form description instead -- the Lite-path direct-entry shortcut: binds{name}=aid-deploy,{verb}=deploy,{artifact}=""(bare verb),{description}=<the given text>, then delegates to the shared shortcut engine (.claude/aid/templates/shortcut-engine.md,INTAKE -> ... -> APPROVAL-HALT), scaffolding a flattened Lite work and running the grading gates. Never executes -- it halts for approval; this shortcut entry does not replace the pipeline role below, it adds a second, independent entry point to the same skill directory.
Workspace
.aid/
knowledge/
STATE.md ← Q&A, Review History (settings → .aid/settings.yml), Q&A (Pending)
.aid/works/{work}/
STATE.yml ← Deploy State (current operation status, history)
packages/ ← product (one file per release)
package-001-{name}.md
package-002-{name}.md
PLAN.md ← deliveries and sequencing
deliveries/delivery-NNN/tasks/task-NNN/ ← full path: task files with statuses
tasks/task-NNN/ ← lite path: task files with statuses (no delivery-NNN/ nesting)
features/ ← feature SPECs
What ships with it
6 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.
- 9d ago First seen · 204 lines · 52 tokens per session scan A 0e8a4c3d64c2
aid-deploy is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 2,620 once invoked, about $0.0003 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.