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-governednpx skills add layer1labs/specsmith --skill warp-governedgit clone --depth 1 https://github.com/layer1labs/specsmithWrote 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/layer1labs/specsmith/warp-governed)<a href="https://agentmods.dev/skills/layer1labs/specsmith/warp-governed"><img src="https://agentmods.dev/badge/skills/layer1labs/specsmith/warp-governed.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.00000 | $0.00500 |
| Opus 5 | $0.00000 | $0.00250 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
warp-governed 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL.md
Warp Governed Profile
Requirements Covered
Governance Requirements
- REQ-012: Least-Privilege Agent Permissions
- REQ-217: Agent Permissions Check
- REQ-220: Policy Guardrails
- REQ-244: Context Window Sizing
- REQ-245: Live Context Fill Indicator
- REQ-246: Auto Context Compression
- REQ-247: Hard Context Ceiling
Core Principle
The warp-governed profile is designed for agents operating within the Warp Terminal environment. It ensures compliance with Specsmith governance while leveraging Warp's specific capabilities and constraints.
Profile Characteristics
Required Skills
- preflight-gate
- governed-agent-loop
- requirement-author
- testcase-author
- traceability-auditor
- context-pack-compiler
- token-budget-auditor
- skill-composer
- warp-integration
Environment-Specific Features
- Warp Terminal integration capabilities
- Context window optimization for Warp's terminal constraints
- Compliance with Warp's terminal environment
- Integration with Warp's native terminal features
Implementation Details
Warp-Specific Execution
- Leverage Warp Terminal's native capabilities for terminal operations
- Optimize context windows to fit Warp's terminal constraints
- Apply Specsmith governance rules within Warp's environment
- Maintain traceability between Warp actions and Specsmith requirements
Context Management
- Optimize context for Warp's terminal environment
- Apply Warp-specific compression techniques
- Ensure context fits within Warp's constraints while maintaining traceability
- Track Warp-specific terminal usage
Configuration
Default Behavior
By default, the warp-governed profile:
- Integrates with Warp Terminal's native features
- Optimizes context for Warp's terminal environment
- Maintains full Specsmith governance compliance
- Tracks Warp-specific usage metrics
Override Options
- Allow Warp-specific skill overrides
- Support Warp Terminal environment customization
- Enable Warp-specific context optimization
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 · 76 lines · 0 tokens per session scan A 0dc85deec0e3
warp-governed is a skill published in the GitHub repository layer1labs/specsmith (7 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 500 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…