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-spec/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-spec)<a href="https://agentmods.dev/skills/davidmatousek/tachi/aod-spec"><img src="https://agentmods.dev/badge/skills/davidmatousek/tachi/aod-spec.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.00071 | $0.01617 |
| Opus 5 | $0.00036 | $0.00809 |
| Sonnet 5 | $0.00014 | $0.00323 |
| Haiku 4.5 | $0.00007 | $0.00162 |
Grade A, and why
~aod-spec 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 3d 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-spec — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Validator Skill
Purpose
Automatically validates specification files (spec.md) for completeness, quality, and readiness for architecture and implementation phases. Implements FR-004 from the feature specification.
How It Works
Step 1: Locate Specification
- Search for
specs/*/spec.mdfiles in the repository - If specific feature directory provided, validate that spec.md
- Report if spec.md not found
Step 2: Validate Mandatory Sections
Check for required sections per specification template:
-
User Scenarios & Testing (mandatory)
- User stories with acceptance scenarios
- Independent test criteria
- Edge cases identified
-
Requirements (mandatory)
- Functional requirements
- Key entities
-
Success Criteria (mandatory)
- Measurable outcomes
-
Scope (mandatory)
- In scope
- Out of scope
-
Assumptions (optional but recommended)
-
Dependencies (optional but recommended)
-
References (optional)
Step 3: Check for Clarification Markers
- Grep for
[NEEDS CLARIFICATION]markers - Report all instances with line numbers
- Specification not ready if any markers remain
Step 4: Validate Testable Criteria
- Check that each user story has clear acceptance scenarios
- Verify success criteria are measurable (contain numbers/percentages)
- Ensure requirements have validation criteria
Step 5: Check Scope Boundaries
- Verify "In Scope" section exists and is populated
- Verify "Out of Scope" section exists (clear boundaries)
- Check that scope is clearly bounded (not open-ended)
Step 6: Generate Validation Report
Report format:
Specification Validation Report
File: specs/{feature-id}/spec.md
Mandatory Sections:
- [✓/✗] User Scenarios & Testing
- [✓/✗] Requirements (Functional Requirements)
- [✓/✗] Success Criteria
- [✓/✗] Scope (In/Out)
Quality Checks:
- [✓/✗] No [NEEDS CLARIFICATION] markers
- [✓/✗] All requirements testable
- [✓/✗] Scope clearly bounded
- [✓/✗] Success criteria measurable
Status: READY / NOT READY
Issues Found:
1. [Issue description with line number]
2. [Issue description with line number]
Recommendations:
- [Specific action to resolve each issue]
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.
- 3d ago First seen · 214 lines · 71 tokens per session scan A 9e195194072b
~aod-spec is a skill published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 24d ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,617 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
sast-dast-coordinator
../../../appsec-devsecops/sast-dast-coordinator/SKILL.md.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
race-condition
Race condition / TOCTOU exploitation — concurrent and parallel-request attacks against web applications that check then act, write session state before validating it, or perform slow operations that widen the race window. Covers single-endpoint races (double-spend, coupon abuse, balance overflow) and multi-endpoint…
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
testing-mcp-server-security
Testing Model Context Protocol (MCP) servers and the clients that consume them for tool poisoning, prompt injection via tool descriptions/outputs, over-permissioned and local-credential-stealing tools, config/trust bypasses, and unauthenticated RCE during authorized penetration tests of AI agent infrastructure.
container-image-scan
../../../cloud-infra/container-image-scan/SKILL.md.