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 kunalsuri/ai-fication-kit --skill add-featuregit clone --depth 1 https://github.com/kunalsuri/ai-fication-kitWrote 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/kunalsuri/ai-fication-kit/add-feature)<a href="https://agentmods.dev/skills/kunalsuri/ai-fication-kit/add-feature"><img src="https://agentmods.dev/badge/skills/kunalsuri/ai-fication-kit/add-feature.svg" alt="Measured on agentmods" 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.00044 | $0.00547 |
| Opus 5 | $0.00022 | $0.00273 |
| Sonnet 5 | $0.00009 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
add-feature 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 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.
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.
What it actually says
Add a feature
The contract: no code before a spec, no edits to frozen code, no "done" without green tests, no merge without a review and a knowledge update.
1. Spec
If ai/lab/specs/SPEC_<name>.md doesn't exist, draft it from SPEC_TEMPLATE.md
(goal, scope, touch list, acceptance criteria, verification). Get the user's OK.
2. Locate
ai/guide/MODULE_MAP.md→ which modules; note Stability of every target.ai/analysis/FEATURE_CATALOG.md→ the "where new code lives" decision tree and the 3-file rule for related features.ai/lab/WORKLOG.md→ recent history: was this area just changed? is the behavior deliberate?- Keep broad reading read-only and cheap (directory listings, manifests, search hits over whole-file reads) to protect context.
3. Gate
Any file in the touch list with Stability frozen or ? ⇒ stop and ask the human.
Record their approval in the spec before proceeding.
4. Implement
Make the smallest diff that satisfies the spec. Conventions per
ai/guide/CONVENTIONS.md — see also reference/checklist.md. Match the license
headers of neighboring files. No drive-by refactors, no layout changes, no
dependency additions unless the plan says so.
5. Verify
Run the narrowest suite that covers the change first, then the suite(s) the spec names. Report command run · exit status · failures verbatim. Red or unrun ⇒ not done.
6. Update knowledge
FEATURE_MAP entry; catalog amendment; MODULE_MAP if layout changed; all [inferred].
Tell the user which tags await their [verified] flip.
7. Review & record
Request /review-change on the diff (fresh context — not this session). Append
the work's row to ai/lab/WORKLOG.md linking spec, review, and commits, and move the
feature's ai/lab/ROADMAP.md row from Planned to Shipped (cross-link spec, WORKLOG
row, and PR by feature ID).
What ships with it
1 file 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.
- 8d ago First seen · 48 lines · 44 tokens per session scan A 2d19efd34d33
add-feature is a skill published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed 5d ago), licensed Apache-2.0. It adds 44 tokens to every session and 547 once invoked, about $0.0002 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
close-my-loops
Build and maintain a personal work profile and open-loop tracker for the user's own job — a markdown file covering their org, key contacts, communication style, active initiatives, and open loops synthesized from their own email/Slack; a Cowork Project setup so that file is actually read every session; a scheduled…
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
anti-sleep
Keep a Mac awake with caffeinate during long builds, downloads, or supervised automation runs.
accint-commitments
Triage acc's open promises and close them with honest real-world verdicts via accact(runtime="outcome").
gsd-surface
Toggle which skills are surfaced — apply a profile, list, or disable a cluster without reinstall.
gsd-capture
Capture ideas, tasks, notes, and seeds to their destination.