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/obsidian-owl/specwright/gate-wiringnpx skills add Obsidian-Owl/specwright --skill gate-wiringgit clone --depth 1 https://github.com/Obsidian-Owl/specwrightWrote 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/obsidian-owl/specwright/gate-wiring)<a href="https://agentmods.dev/skills/obsidian-owl/specwright/gate-wiring"><img src="https://agentmods.dev/badge/skills/obsidian-owl/specwright/gate-wiring.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.00040 | $0.01805 |
| Opus 5 | $0.00020 | $0.00903 |
| Sonnet 5 | $0.00008 | $0.00361 |
| Haiku 4.5 | $0.00004 | $0.00180 |
Grade A, and why
gate-wiring 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gate: Wiring
Goal
Ensure the codebase is properly connected — no dead code, no orphaned files, no architecture violations. Code that compiles and passes tests can still be wired incorrectly.
Inputs
{projectArtifactsRoot}/config.json-- architecture layers, project structure{repoStateRoot}/work/{selectedWork.id}/workflow.json-- selected work unit- Changed files (via
git diff)
Outputs
- Evidence file at
{workDir}/evidence/wiring-report.md - Gate status in the selected work's
workflow.json - Findings with specific file:line references and remediation
Constraints
Scope (MEDIUM freedom):
- Focus on changed files and their immediate dependents.
- Use
git diff --name-onlyagainst main branch.
Analysis (HIGH freedom):
- Delegate to
specwright-architectfor structural analysis. - The architect checks:
- Unused exports: Public functions/types exported but never imported.
- Orphaned files: Files not imported by anything in the dependency graph.
- Layer violations: Imports crossing architecture layer boundaries (e.g., UI importing directly from database layer). Layers from
config.jsonarchitecture.layers. - Circular dependencies: Import cycles that may cause runtime issues.
- Use real tooling when available (e.g.,
madge,knip,ts-prune). - Fall back to LLM analysis when tools aren't configured.
Verdict (LOW freedom):
- Follow
protocols/evidence.md#verdict-rendering. - WARN severity for most findings (wiring issues rarely block functionality).
- BLOCK only for circular dependencies in changed files.
- This gate is advisory — it helps clean up, not block shipping.
Cross-unit integration (MEDIUM freedom, multi-unit only):
When verifying the final unit of a multi-unit design, run additional cross-unit wiring checks against the full feature diff. This catches integration issues invisible to per-unit analysis: missing cross-unit imports, interface mismatches, disconnected entry points.
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.
- 5d ago First seen · 170 lines · 40 tokens per session scan A 176771e740ad
gate-wiring is a skill published in the GitHub repository Obsidian-Owl/specwright (9 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,805 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
rust-skills
Rust best practices — 179 rules across 14 categories for idiomatic, optimized Rust code.
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
llm-friendly-context
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
cco-task
Organize work by task, track tokens/cost per task, and keep a small patchable execution state that is re-injected after /compact (SKILL.state-style) — start a task, patch its state, list tasks, or mark the active one done. Pairs with /cco-pack to load minimal context per task.
cco-templates
Manage context templates for common task types.
discuss
Use when exploring a feature idea before committing, or revisiting a parked one. Triggers — "/engineer.discuss", "/engineer.discuss ", "I have an idea about", "should we build", "let's think about".