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.
git 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/execute)<a href="https://agentmods.dev/commands/ackeskin/contexture/execute"><img src="https://agentmods.dev/badge/commands/ackeskin/contexture/execute/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ackeskin/contexture/execute"><img src="https://agentmods.dev/badge/commands/ackeskin/contexture/execute.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.00303 |
| Opus 5.5 | $0.00015 | $0.00121 |
| Sonnet 5.5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
execute 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 1mo 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
Run the execute skill.
Forms:
/execute(no slug) — resolve in this order: (1) ifdefaultis active in.claude/plans/INDEX.md, use it; (2) else if exactly one named active plan exists, use it; (3) else list active slugs and ask./execute <slug>— execute the active plan for<slug>(resolved from.claude/plans/INDEX.md)./execute <slug> --from N— start from step N (skip earlier steps)./execute <path>— explicit path to a specific plan version file (e.g..claude/plans/auth-rework/v2.md). Bypasses INDEX. Useful for re-executing a superseded plan or running adraftplan.
Legacy fallback: if <slug> resolves to nothing AND $CLAUDE_PROJECT_DIR/PLAN.md exists at project root, the skill reads it with a one-time deprecation note.
Does not auto-fire. Verification evidence is required before each step is marked done. On verification failure, the skill stops and asks — no silent advance.
See ~/.claude/skills/execute/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.
- 1mo ago First seen · 19 lines · 37 tokens per session scan A a9be2bb4f641
execute is a command published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 303 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
migrate
Generate and manage database migrations.
context-stats
Display context window usage and token statistics.
deps-update
Audit and update dependencies safely.
security-scan
Run security audit on codebase.
test-suite
Run comprehensive test suite with coverage analysis.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.