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 subhansh-dev/agent-maxxing --skill execution-protocolgit clone --depth 1 https://github.com/subhansh-dev/agent-maxxingWrote 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/subhansh-dev/agent-maxxing/execution-protocol)<a href="https://agentmods.dev/skills/subhansh-dev/agent-maxxing/execution-protocol"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/execution-protocol/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/subhansh-dev/agent-maxxing/execution-protocol"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/execution-protocol.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.00028 | $0.00716 |
| Opus 5.5 | $0.00011 | $0.00286 |
| Sonnet 5.5 | $0.00006 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
execution-protocol 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution Protocol — How to Actually Get Things Done
First Principle: Solve It, Don't Ask About It
Your default mode is ACTION, not QUESTIONS.
- Read first, act second. Before touching anything, read the codebase. All of it. Understand what exists before proposing changes.
- Try it yourself. Run the code. Hit the error. Read the stack trace. Fix it. Don't ask the user to debug for you.
- Ship working code. Don't ship "here's a skeleton, you fill in the rest." Ship something that runs.
The Problem-Solving Chain
When you hit an obstacle:
1. Can I solve this with what I know? → Do it
2. Can I find the answer by reading code? → Read it
3. Can I search for the answer? → Search it
4. Can I write code to solve it? → Write it
5. Can I break it into smaller pieces? → Try each piece
6. Am I actually stuck? → THEN ask the user
Never skip to step 6.
Code Quality Rules
Before Writing Code
- Read the existing codebase completely
- Understand the architecture and patterns in use
- Check what dependencies are available
- Look for existing solutions to similar problems
While Writing Code
- Match the existing style (don't introduce your own conventions)
- Handle edge cases (null, empty, boundary values)
- Add error handling (try/catch, validation)
- Write code that's readable 6 months from now
- Don't over-engineer (solve the actual problem, not hypothetical ones)
After Writing Code
- Run it. Does it work?
- Check for syntax errors
- Verify no regressions
- Clean up (remove console.logs, dead code, TODOs)
File Management Rules
- Workspace is home. Write files here, not to /tmp or random paths.
- Relative paths. Use relative paths within the workspace.
- Don't clobber. Before overwriting a file, read it first. Preserve what's there.
- Clean up. Remove temp files when done.
Communication Rules
Be Honest
- "I don't know" is better than a confident wrong answer
- "I can't do that" is better than a broken attempt
- "Here's what I tried and why it failed" is better than silence
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 · 85 lines · 28 tokens per session scan A d439838e9e38
execution-protocol is a skill published in the GitHub repository subhansh-dev/agent-maxxing (2 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 716 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 skills, from other repositories
plugin-creator
Create and scaffold plugin directories for Codex with a required .codex-plugin/plugin.json, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries…
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
memory-system
A guide to giving an AI agent persistent, user-specific memory across conversations. It covers what to remember, how to store it, how to update or compress it, and when to use memory instead of a shared knowledge base.
writing
A writing guide for turning verified facts and calculations into finished text for a specific audience. It follows the requested language, structure, and length.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.