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 agents/zyqzyq/unfour/execution_protocolgit clone --depth 1 https://github.com/zyqzyq/UnfourWhat 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.00000 | $0.01409 |
| Opus 5 | $0.00000 | $0.00705 |
| Sonnet 5 | $0.00000 | $0.00282 |
| Haiku 4.5 | $0.00000 | $0.00141 |
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 yesterday.
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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution Protocol
Default execution workflow for AI coding agents working on implementation or documentation tasks in this repository.
1. Role And Authority
Document precedence (highest to lowest):
AGENTS.mdfor repository-wide rules and architecture constraints.- Task-specific prompt for current goal, scope, and acceptance criteria.
docs/agents/START_HERE.mdfor context loading strategy.- Domain documentation under
docs/architecture/,docs/ui/,docs/mcp/,docs/testing/, anddocs/release/. - Package or crate
AGENTS.md/README.md. - This file for default workflow and reporting conventions.
When a task prompt conflicts with AGENTS.md, follow AGENTS.md and report
the conflict.
2. Start-Of-Task Checklist
Before writing code or documentation:
- Read
AGENTS.md. - Read
docs/agents/START_HERE.mdand follow its scoped reading order. - Read task-specific files listed in the prompt.
- Read relevant domain docs, such as package boundaries for dependency changes or UI docs for interaction changes.
- Run
git status --shortto inspect the working tree. - Inspect the current diff before editing.
- Confirm the requested scope and identify verification commands.
Begin execution directly after a short plan unless a critical ambiguity makes safe execution impossible. If blocked, state the ambiguity and stop.
3. Scope Discipline
- Modify only files necessary for the requested task.
- Do not perform opportunistic refactors, dependency upgrades, or unrelated formatting.
- Do not change public contracts, exported types, store shape, or Tauri command behavior unless the task requires it.
- Record out-of-scope issues in the final report under remaining risks instead of fixing them.
- Stop and report when a required change would cross an explicitly forbidden boundary.
4. Change Discipline
- Prefer small, reviewable changes over large rewrites.
- Preserve existing behavior unless the task explicitly requests behavior changes.
- Keep architecture boundaries intact.
- Do not add
any,@ts-ignore, or@ts-expect-errorunless the task explicitly justifies it. - Do not introduce silent fallbacks or hide errors to make builds pass.
- Reuse existing project patterns before adding new abstractions.
- Do not create new documentation files unless the task requires them.
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.
- yesterday First seen · 170 lines · 0 tokens per session scan A d202242adbd5
EXECUTION_PROTOCOL is an agent published in the GitHub repository zyqzyq/Unfour (2 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,409 tokens. 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 agents, from other repositories
altai-implementer
Implements one bounded ALTAI roadmap slice and its tests. Default working agent for roadmap PRs.
altai-explorer
Read-only ALTAI repository exploration. Use when file ownership or existing patterns are unclear before implementing a roadmap item.
altai-reviewer
Read-only diff review for a risky ALTAI PR. Reports actionable findings only.
altai-test-triage
Triages failing tests/logs into product defects, flaky tests, environment problems, and pre-existing failures.
Test Engineer
Writes tests first, then implementation. Strict TDD.
researcher
Sample subagent that does focused research on a single question.