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 skills add AcKeskin/contexture --skill executegit 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/skills/ackeskin/contexture/execute)<a href="https://agentmods.dev/skills/ackeskin/contexture/execute"><img src="https://agentmods.dev/badge/skills/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/skills/ackeskin/contexture/execute"><img src="https://agentmods.dev/badge/skills/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.00067 | $0.06051 |
| Opus 5.5 | $0.00027 | $0.02420 |
| Sonnet 5.5 | $0.00013 | $0.01210 |
| Haiku 4.5 | $0.00007 | $0.00605 |
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.
How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
execute
The execute organ. Consumes prep for per-step rule re-load on boundary crossings; consumes discover indirectly via prep.
Execute is the implementation phase of the spec → plan → execute → review → close-out workflow. It runs a plan step-by-step with verification gates. It does not plan, does not draft, does not commit.
When to run
Manual only. User invokes /execute [slug | path] [--from N].
Do not auto-fire:
- Not at session start.
- Not after
/draft-planfinishes — the user must review the plan first. - Not on any hook — this skill implements code changes, that's always user-initiated.
Inputs
- Plan resolution. One of:
- Slug (
/execute <slug>) — resolve to.claude/plans/<slug>/v<N>.mdwhere N is the active version per.claude/plans/INDEX.md. - No argument — resolve against
.claude/plans/INDEX.mdper draft-plan's canonical slug-resolution cascade (draft-plan SKILL.md § Forms):defaultif active, else the single active slug, else list active slugs and ask. - Explicit path (
/execute <path>) — use the path verbatim. Required when targeting a non-active version. - Legacy fallback — if no slug / path resolves AND
$CLAUDE_PROJECT_DIR/PLAN.mdexists at project root, use it with a one-time deprecation note: "Reading legacy PLAN.md at project root — new plans go under.claude/plans/<slug>/v<N>.md. Run/draft-plan <slug>to migrate."
- Slug (
- Starting step. Default: 1. Override via
--from N— skips steps 1..N-1 (assumes they were done outside the skill). - User confirmation on delegation prompts and on verification failures. Collaborator principle — no silent choices.
Procedure
1. Load the plan
Resolve the plan file per the input rules above. Bail if no plan resolves:
No plan found. Run /draft-plan first, or pass an explicit path: /execute .
When multiple active plans exist and no slug was given, list them and stop:
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 · 334 lines · 67 tokens per session scan A 9a93f96dc34a
execute is a skill published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 6,051 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
jira-validate-production
Check that the fix a Jira issue carries is live on the PRODUCTION site and behaves as the issue asked, then close the card, or open a follow-up issue for what failed. Insert into the prompt of a run started on a batch of merged issues, or of a Jira post-deploy column rule.
jira-qa-gate
Decide whether a reviewed Jira issue can skip the team's own QA and go straight to the next column, or stays for a person. Insert into the prompt of the Jira column reviewed work waits in before the client sees it.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
operations
Operations excellence expertise for supply chain optimization, process improvement (Lean, Six Sigma), capacity planning, vendor management, quality assurance, and operational efficiency. Use when optimizing processes, managing supply chains, or improving operational performance.