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/write-testsgit 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/write-tests)<a href="https://agentmods.dev/commands/ackeskin/contexture/write-tests"><img src="https://agentmods.dev/badge/commands/ackeskin/contexture/write-tests.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.00046 | $0.00297 |
| Opus 5 | $0.00023 | $0.00148 |
| Sonnet 5 | $0.00009 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
write-tests 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 write-tests skill for the current context.
/write-tests <target> authors a quality test suite for existing code (a function, class, module, or file). Examples:
/write-tests— prompts for a target./write-tests src/billing/Invoice.cs— tests that file./write-tests calculateRetryBudget— tests that function.
The skill detects the project's test framework + conventions (reusing the extracted test conventions where present), proposes a test plan (cases + rationale) for your accept/edit/reject before writing anything, then delegates idiomatic authoring to the scope's language-pro agent. Its default stance is characterization-with-flags: it pins the code's current behavior as tests (so you can refactor safely) but flags anything that looks like a bug for you to confirm rather than silently asserting it correct. Optionally runs the suite; on a failure it surfaces the test-vs-code discrepancy rather than auto-adjusting, and reports what it covered AND what it deliberately did not.
Mode A only — never auto-fires. See ~/.claude/skills/write-tests/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 · 16 lines · 46 tokens per session scan A eed3d8f8dfde
write-tests is a command published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 297 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-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.
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.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.