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 commands/ackeskin/contexture/specgit clone --depth 1 https://github.com/AcKeskin/contextureWrote 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/commands/ackeskin/contexture/spec)<a href="https://agentmods.dev/commands/ackeskin/contexture/spec"><img src="https://agentmods.dev/badge/commands/ackeskin/contexture/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.1 | $0.00064 | $0.00244 |
| Opus 5 | $0.00032 | $0.00122 |
| Sonnet 5 | $0.00013 | $0.00049 |
| Haiku 4.5 | $0.00006 | $0.00024 |
Grade A, and why
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 yesterday.
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
Run the spec skill for the current context.
Forms:
/spec— write to the reserveddefaultslug (project itself is the scope)./spec <slug>— named slug; createv1.mdif new, else evolve the active version./spec <slug> --new— explicit fresh slug; refuse if<slug>already exists in INDEX./spec <slug> --abandon— mark the active versionabandoned; no new file written.
The skill interviews the user, runs a done-criteria probe, grounds the spec via /discover, writes the versioned file under .claude/specs/<slug>/, and reconciles INDEX.md. It does not implement, plan, or execute.
See ~/.claude/skills/spec/SKILL.md for the full procedure.
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.
- yesterday First seen · 17 lines · 64 tokens per session scan A 5228793b4e89
spec is a command published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 244 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 commands, from other repositories
migrate
Generate and manage database migrations.
test-suite
Run comprehensive test suite with coverage analysis.
context-stats
Display context window usage and token statistics.
security-scan
Run security audit on codebase.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.