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 taurus42119-stack/godkiller-mcp --skill shellgit clone --depth 1 https://github.com/taurus42119-stack/godkiller-mcpWrote 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/taurus42119-stack/godkiller-mcp/shell)<a href="https://agentmods.dev/skills/taurus42119-stack/godkiller-mcp/shell"><img src="https://agentmods.dev/badge/skills/taurus42119-stack/godkiller-mcp/shell/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/taurus42119-stack/godkiller-mcp/shell"><img src="https://agentmods.dev/badge/skills/taurus42119-stack/godkiller-mcp/shell.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.00036 | $0.00187 |
| Opus 5.5 | $0.00014 | $0.00075 |
| Sonnet 5.5 | $0.00007 | $0.00037 |
| Haiku 4.5 | $0.00004 | $0.00019 |
Grade A, and why
shell 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.
This is a copy
100% identical to shell — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Run Shell Commands
Use this skill only when the user explicitly invokes /shell.
Behavior
- Treat all user text after the
/shellinvocation as the literal shell command to run. - Execute that command immediately with the terminal tool.
- Do not rewrite, explain, or "improve" the command before running it.
- Do not inspect the repository first unless the command itself requires repository context.
- If the user invokes
/shellwithout any following text, ask them which command to run.
Response
- Run the command first.
- Then briefly report the exit status and any important stdout or stderr.
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 · 25 lines · 36 tokens per session scan A b354ce28c70a
shell is a skill published in the GitHub repository taurus42119-stack/godkiller-mcp (27 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 187 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to shell, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ag-sdd
Activates the Anti-Gravity Spec-Driven Development (ag-sdd) workflow. Use this skill when the user asks to implement a feature, fix a bug, or write code in a repository that uses ag-sdd. It enforces a strict 4-phase SDD lifecycle: Discovery, Spec Generation, Sequential Execution, and Quality Signoff.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
cao-workflow
Author and run CAO Python workflow scripts — multi-step, parameterized, fan-out orchestrations executed by cao workflow run. Use when the user wants a repeatable multi-step job (e.g. data analysis over many files, a review pipeline, a parameterized batch). Authoring ends at a validated script file; running it is a…
aidlc-portfolio
Coordinate multiple AI-DLC workflows across repositories and Git worktrees using an evidence-backed portfolio catalog and deterministic workspace tooling. Use when initializing an AI-DLC portfolio workspace, discovering organization or business context, registering projects and dependencies, creating child intents and…
cao-plugin
Create a new CAO (CLI Agent Orchestrator) plugin. Use this skill whenever the user wants to add a plugin that reacts to CAO lifecycle or messaging events, scaffold a plugin package, understand plugin requirements, or integrate an external system (Discord, Slack, dashboards, logging, metrics) with CAO. Also use when…
cao-mcp-apps
Enable, operate, and extend CAO's MCP Apps surface — the host-rendered fleet dashboard visible inside MCP App hosts (Claude Desktop, ChatGPT, VS Code Copilot, Goose, Postman). Use when the user says "enable MCP Apps in CAO", "the ui://cao views aren't rendering", "rebuild MCP Apps bundles", "add a new ui://cao/ view"…