Borrowing it
Nothing to install: this file belongs to davidmatousek/tachi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davidmatousek/tachi/main/.claude/skills/~aod-kickstart/SKILL.mdgit clone --depth 1 https://github.com/davidmatousek/tachiWrote 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/davidmatousek/tachi/aod-kickstart)<a href="https://agentmods.dev/skills/davidmatousek/tachi/aod-kickstart"><img src="https://agentmods.dev/badge/skills/davidmatousek/tachi/aod-kickstart.svg" alt="Measured on agentmods" 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.00088 | $0.03975 |
| Opus 5 | $0.00044 | $0.01988 |
| Sonnet 5 | $0.00018 | $0.00795 |
| Haiku 4.5 | $0.00009 | $0.00398 |
Grade A, and why
~aod-kickstart 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ~aod-kickstart — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aod.kickstart Skill
Purpose
Transform a project idea into a sequenced consumer guide with 6-10 seed features ready for the AOD lifecycle. The skill runs three stages:
- Idea Intake -- Capture the project idea, target user, and key capabilities through structured prompts
- Stack Selection -- Detect an active stack pack or guide the developer to select/describe a stack
- Guide Generation -- Produce a consumer guide at
docs/guides/CONSUMER_GUIDE_{PROJECT_NAME}.mdwith setup phases, a feature summary table, and per-feature seed blocks ordered for incremental value delivery
Each seed feature block is structured for direct copy-paste into /aod.discover.
Prerequisites Check
Before starting, validate the output directory exists.
- Use Glob to check for
docs/guides/directory - If
docs/guides/does not exist, display the following error and stop:
ERROR: docs/guides/ directory not found.
Run `make init` to set up project structure.
Do not proceed to Stage 1 until docs/guides/ is confirmed to exist.
Stage 1: Idea Intake
Capture the project idea through 5 structured prompts. Store responses in variables for use in later stages.
Step 1.1: Capture Idea Description
Use AskUserQuestion:
Question: "Describe your project idea (what are you building and why?)"
Store the response as {idea_description}.
Vagueness validation (FR-014): Count the words in the response. If fewer than 20 words, ask for elaboration:
Question: "Your idea description is brief. Add more detail about what the project does, the problem it solves, or key workflows (aim for 2-3 sentences)."
Allow up to 2 rounds of clarification. If still under 20 words after 2 rounds, accept the response as-is and proceed with a note:
Note: Idea description is brief. The generated guide may need refinement.
Step 1.2: Capture Target User
Use AskUserQuestion:
Question: "Who is the target user for this project?"
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.
- 4d ago First seen · 371 lines · 88 tokens per session scan A 3c30c5ae79bf
~aod-kickstart is a skill published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 25d ago), licensed Apache-2.0. It adds 88 tokens to every session and 3,975 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
usap-program-manager
Security program manager and passive lifecycle orchestrator (cs-security-program-manager). Use for security roadmap planning, program health scanning, debt tracking, facilitated reviews, or when the user says "security roadmap", "program planning", "security debt", "proactive scan", or "program review".
usap-red-teamer
Offensive security coordinator (cs-red-teamer). Use for red team campaign planning, attack path analysis, engagement scoping, adversary simulation, or when the user says "red team", "pentest", "attack simulation", "run an engagement", or "offensive security". Requires explicit authorization scope.
usap-alex
Universal USAP security advisor (cs-security-analyst). Use for any security question, alert triage (AT), threat hunt (TH), compromise assessment (CA), or when the user says "activate Alex", "start USAP", or asks what USAP can do.
usap-ciso
CISO and executive security advisor (cs-ciso-advisor). Use for board reports, executive risk briefings, regulatory gap assessments, cyber insurance inputs, or when the user says "board report", "CISO brief", "executive summary", "risk posture for leadership", or "regulatory update".
usap-incident-responder
Active incident command and response (cs-incident-responder). Use when there is a confirmed or suspected active incident, for containment decisions, forensic investigation, SEV declaration, or when the user says "declare incident", "start IR", "we have an active breach", or "forensics".
nuclei
Nuclei CLI parameter reference and usage patterns - YAML-template vulnerability scanning, target input modes, template filters, output formats, rate limits, ProjectDiscovery dashboard upload, and common scan commands.