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-project-plan/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-project-plan)<a href="https://agentmods.dev/skills/davidmatousek/tachi/aod-project-plan"><img src="https://agentmods.dev/badge/skills/davidmatousek/tachi/aod-project-plan.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.00059 | $0.01850 |
| Opus 5 | $0.00030 | $0.00925 |
| Sonnet 5 | $0.00012 | $0.00370 |
| Haiku 4.5 | $0.00006 | $0.00185 |
Grade A, and why
~aod-project-plan 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-project-plan — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Validator Skill
Purpose
Automatically validates architecture documentation (plan.md) for completeness, technical rigor, and alignment with feature specifications. Implements FR-006 from the feature specification.
How It Works
Step 1: Locate Architecture Plan
- Search for
specs/*/plan.mdfiles - If specific feature directory provided, validate that plan.md
- Report if plan.md not found
Step 2: Validate Required Sections
Check for mandatory sections per AOD plan template:
Technical Context (Required)
- Language/Version
- Primary Dependencies
- Storage solution
- Testing approach
- Target Platform
- Project Type
- Performance Goals
- Constraints
- Scale/Scope
Constitution Check (Required)
- All 7 constitutional principles validated
- Evidence for each principle
- Violations justified (if any)
Project Structure (Required)
- Documentation structure
- Source code structure
- File organization
Technology Stack (Required)
- Languages and versions
- Frameworks and libraries
- Database and storage
- Infrastructure components
Step 3: Check Technical Decisions
Verify technical decisions are documented:
- data-model.md: Entity definitions and relationships
- contracts/: API specifications (if applicable)
- research.md: Technical unknowns resolved
Step 4: Validate Spec Alignment
- Compare plan.md with spec.md
- Check all functional requirements addressed
- Verify success criteria have implementation strategy
- Ensure out-of-scope items respected
Step 5: Security Architecture Check
Verify security considerations documented:
- Authentication approach
- Authorization model
- Data protection strategy
- API security measures
- Secrets management
Step 6: Generate Validation Report
✅ Architecture Validation Report
File: specs/{feature-id}/plan.md
Required Sections:
- [✓/✗] Technical Context
- [✓/✗] Constitution Check (7/7 principles)
- [✓/✗] Project Structure
- [✓/✗] Technology Stack
Design Artifacts:
- [✓/✗] data-model.md (entities defined)
- [✓/✗] contracts/ (API specs)
- [✓/✗] research.md (decisions documented)
Quality Checks:
- [✓/✗] All FRs from spec.md addressed
- [✓/✗] Security architecture documented
- [✓/✗] Performance targets specified
- [✓/✗] Complexity justified
Status: READY / NOT READY
Issues Found:
1. [Issue description]
2. [Issue description]
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.
- 4d ago First seen · 263 lines · 59 tokens per session scan A d042b8f306cf
~aod-project-plan is a skill published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 26d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,850 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-09-03.
Other skills, from other repositories
deserialization-exploitation
Insecure deserialization — RCE via malicious serialized objects in Java (ysoserial), PHP (PHPGGC), .NET (ysoserial.net), and Python (pickle). Covers gadget chain selection, payload generation, and injection into cookies, POST bodies, ViewState, and API endpoints.
ssti-exploitation
Server-Side Template Injection (SSTI) — RCE through template engines. Covers Jinja2 (Python/Flask), Twig (PHP/Symfony), Freemarker (Java), ERB (Ruby), Razor (.NET). Includes engine fingerprinting, MRO chain construction, and filter bypass.
ssrf-exploitation
Server-Side Request Forgery (SSRF) — exploiting server-side URL fetching to access internal services, cloud metadata (AWS/GCP/Azure), internal APIs, and port scanning. Covers IP bypass techniques, DNS rebinding, Gopher protocol smuggling, and redirect-based bypass.
web-app-pentest
../../../pentest/web-app-pentest/SKILL.md.
api-enumeration
REST API discovery, GraphQL detection, parameter fuzzing.
idor-exploitation
Insecure Direct Object References (IDOR) — authorization bypass through predictable object references (sequential IDs, UUIDs, filenames, encoded IDs). Covers horizontal/vertical privilege escalation, ID enumeration, HTTP method tampering, and JWT sub claim manipulation.