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 agentmods add skills/sebaboler/vanguard/tech-specnpx skills add SebaBoler/vanguard --skill tech-specgit clone --depth 1 https://github.com/SebaBoler/vanguardWrote 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/sebaboler/vanguard/tech-spec)<a href="https://agentmods.dev/skills/sebaboler/vanguard/tech-spec"><img src="https://agentmods.dev/badge/skills/sebaboler/vanguard/tech-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 | $0.00051 | $0.00321 |
| Opus 5 | $0.00026 | $0.00161 |
| Sonnet 5 | $0.00010 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
tech-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.
What it actually says
Tech Spec
Research the codebase read-only and produce a precise technical specification for the given task. Do not edit, create, or delete any source files.
Sections to include
Problem
What exactly needs to be solved and why. Identify the gap between the current state and the desired state. Name the stakeholders and the concrete pain point.
Architecture
Components involved, interfaces changed or added, data flows, and integration points with the rest of the system. Include sequence or data-flow sketches if the interaction is non-trivial.
Acceptance Criteria
Numbered, testable conditions that define done. Each criterion must be verifiable without ambiguity.
Tests
Test cases and scenarios that must pass, including edge cases, failure paths, and integration boundaries. Name the test file(s) and key scenarios explicitly.
Risks
Known unknowns, edge cases, backward-compatibility concerns, and failure modes. Call out any assumption that, if wrong, would invalidate the design.
Performance / Scalability
Throughput and latency expectations, growth projections, and any bottleneck or scaling limit introduced or removed by the change.
Output format
Wrap the complete specification in <tech_spec>...</tech_spec>. End with <promise>COMPLETE</promise>.
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 · 39 lines · 51 tokens per session scan A b62327e942ba
tech-spec is a skill published in the GitHub repository SebaBoler/vanguard (4 stars, last pushed 10d ago), licensed MIT. It adds 51 tokens to every session and 321 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
understand-codebase
Understand an unfamiliar codebase or plan a change safely, using Spine's deterministic knowledge-graph MCP tools. Reach for this before answering structural questions about a repo you don't know, before editing code, or when debugging — it hands you engineering decisions (what a change breaks, what's untested, where a…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
openai-whisper-api
Transcribe audio via OpenAI Audio Transcriptions API (Whisper).
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.