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/layer1labs/specsmith/warp-integrationnpx skills add layer1labs/specsmith --skill warp-integrationgit clone --depth 1 https://github.com/layer1labs/specsmithWhat 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.00000 | $0.00438 |
| Opus 5 | $0.00000 | $0.00219 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
warp-integration 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
Warp — specsmith Governance Integration
One-time setup
specsmith integrate warp # generates .warp/ artifacts + .agents/skills/SKILL.md
This writes:
.warp/specsmith-mcp.json— governance MCP server config (identical tospecsmith mcp install-warp).warp/launch_configs/specsmith-governed.yaml— Warp launch configuration that opens a governedspecsmith runsession.agents/skills/SKILL.md— governance skill Warp discovers automatically
For MCP in Warp (Settings → Agents → MCP servers), paste the contents of
.warp/specsmith-mcp.json, or generate it directly:
specsmith mcp install-warp # human-readable instructions
specsmith mcp install-warp --json # raw JSON snippet
specsmith mcp register # register this project (run once per project)
Native REPL awareness
specsmith run detects when it is running inside Warp (via TERM_PROGRAM /
WARP_* env vars) and advertises native integration in its banner and the
ready event frame. Behavior is unchanged outside Warp.
Every Warp session — mandatory protocol
- Run at session start:
specsmith kill-session # idempotent; safe when no processes exist
specsmith audit --project-dir .
specsmith sync --project-dir .
specsmith checkpoint --project-dir .
- Output the checkpoint block verbatim.
- Before every code change:
specsmith preflight "<intent>" --json - Every 8–10 turns:
specsmith checkpoint(output verbatim) - Session end:
specsmith save && specsmith kill-session
Key files
AGENTS.md— universal governance hub (Warp reads this as project Rules).warp/specsmith-mcp.json— governance MCP server config.warp/launch_configs/specsmith-governed.yaml— governed-session launch config.agents/skills/— skill files Warp discovers automatically
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 · 44 lines · 0 tokens per session scan A 8edaa5d5315a
warp-integration is a skill published in the GitHub repository layer1labs/specsmith (7 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 438 tokens. 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
arch-audit
Audit Claude Code architecture files against Anthropic docs and release notes, and verify internal ecosystem consistency. Run on demand to maintain compliance, catch new features, and keep the context system clean.
skill-dev
Code quality audit: detect cross-module coupling, N+1 queries, dead exports, antipatterns, over-large components. Cross-checks against refactoring backlog.
accessibility-audit
Unified accessibility audit - axe-core WCAG 2.2 scan, APCA contrast measurement, static a11y checks (aria-label, tabindex, form labels, focus visibility, onClick on non-interactive). Static and live modes.
pr-review
Autonomous local code review. Reviews either an open PR's diff (via gh) or the local working diff against a base branch (--local, auto-selected when no PR exists yet), spawns a dedicated review subagent with universal + stack-specific severity criteria, posts the review as a comment on the PR (audit trail; skipped in…
responsive-audit
Responsive audit: test pages at 375/768/1024px breakpoints via Playwright. Checks overflow, tap targets, sidebar collapse, text reflow, WCAG 1.4.4 zoom.
security-audit
Security audit: auth/authz on API routes, input validation, row-level access control (RLS in Postgres, ORM scopes or app-level guards elsewhere), response shape review, secret exposure, HTTP headers. Native mode checks entitlements and Keychain. MCP-aware (v1.20+): when mcp-nvd server is wired, Step 3c queries live…