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/wania-kazmi/claude-code-autonomous-agent-workflow/mcp-code-execution-templatenpx skills add Wania-Kazmi/claude-code-autonomous-agent-workflow --skill mcp-code-execution-templategit clone --depth 1 https://github.com/Wania-Kazmi/claude-code-autonomous-agent-workflowWrote 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/wania-kazmi/claude-code-autonomous-agent-workflow/mcp-code-execution-template)<a href="https://agentmods.dev/skills/wania-kazmi/claude-code-autonomous-agent-workflow/mcp-code-execution-template"><img src="https://agentmods.dev/badge/skills/wania-kazmi/claude-code-autonomous-agent-workflow/mcp-code-execution-template.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 | $0.00054 | $0.01120 |
| Opus 5 | $0.00027 | $0.00560 |
| Sonnet 5 | $0.00011 | $0.00224 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
mcp-code-execution-template 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- scripts/execute.py 5.0 KB runs code
- servers/example-server/fetchData.ts 1.6 KB runs code
- servers/example-server/index.ts 566 B runs code
- servers/example-server/processItems.ts 1.3 KB runs code
- servers/example-server/writeResults.ts 1.5 KB runs code
- servers/mcp-client.ts 8.1 KB runs code
- workspace/example-task.ts 2.5 KB runs code
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 · 177 lines · 54 tokens per session scan A c674fb8f6717
mcp-code-execution-template is a skill published in the GitHub repository Wania-Kazmi/claude-code-autonomous-agent-workflow (5 stars, last pushed 7mo ago), with no licence file. It adds 54 tokens to every session and 1,120 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-08-31.
Other skills, from other repositories
grace-cli
Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
grace-execute
Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.
grace-init
Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.
grace-migrate
Agent-applied GRACE 3 to GRACE 4 migration workflow. CLI validates the result but does not convert or delete files.
grace-plan
Read an approved GRACE 4 GraceChangeSpec and optional design context, then create a GraceChangePlan with assertions, scopes, tasks, and verification gates.
grace-spec
Interview the user and create an approved GRACE 4 GraceChangeSpec plus optional design-context.xml inside .grace/changes/active/C-/.