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 instructions/gxfn/wakeflow/claude-mdgit clone --depth 1 https://github.com/GxFn/WakeflowWrote 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/instructions/gxfn/wakeflow/claude-md)<a href="https://agentmods.dev/instructions/gxfn/wakeflow/claude-md"><img src="https://agentmods.dev/badge/instructions/gxfn/wakeflow/claude-md.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.01399 | $0.01399 |
| Opus 5 | $0.00700 | $0.00700 |
| Sonnet 5 | $0.00280 | $0.00280 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
Wakeflow CLAUDE.md 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 4d 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
88% identical to Wakeflow AGENTS.md — 26 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wakeflow Source Repository Instructions For Claude Code
This checkout is the development repository for the Wakeflow Codex and Claude Code plugin artifacts. Work here maintains Wakeflow itself; it is not an installed controller workspace and it does not own the product repositories used to test Wakeflow.
Nested CLAUDE.md files inside plugin artifacts describe the behavior shipped
to installed controller workspaces. They remain product inputs and test
surfaces. Do not mistake their controller-role restrictions for a prohibition
on authorized Wakeflow source maintenance in this repository.
Scope And Safety
- Follow the user's requested scope. Do not expand a Wakeflow change into an Alembic product change or another external repository.
- Preserve pre-existing and unrelated working-tree changes. Inspect
git status --short --branchand the relevant diff before editing. - Do not use destructive Git operations such as
git reset --hard, discard another contributor's changes, or rewrite history unless the user explicitly authorizes that exact operation. - Do not commit, push, tag, publish, or refresh an installed plugin cache unless the user explicitly requests that action. Authorization for one of these actions does not imply authorization for the others.
- Use only explicitly designated disposable workspaces for destructive runtime tests. Never treat a real product repository as a Wakeflow fixture.
- Keep secrets, tokens, private session identifiers, local absolute paths, and machine-specific cache paths out of committed source, fixtures, and docs.
Source Ownership
core/is the canonical source for host-neutral runtime files shared by both plugin artifacts.- Make shared changes in
core/, then runnode tools/sync-core.mjs. Do not directly maintain the generated copies underplugins/codex-wakeflow/orplugins/claude-code-wakeflow/. - After synchronization, run
node tools/sync-core.mjs --checkand inspect the resulting diff in both artifacts. - Host-specific files stay in their artifact. This includes host profiles,
host artifact checks, host send adapters, manifests, host memory files,
READMEs, skills, and template bundles. Claude Code commands and the tmux host
helper also remain Claude-specific. Do not add a host branch to
core/when the difference belongs at a host seam. - Shared code may consume values supplied by a host profile; it must not infer Codex-versus-Claude behavior through ad hoc host checks.
- Treat plugin cache directories as installed outputs, never as source. Modify this checkout first and refresh a cache only from a validated plugin artifact when the user asks for it.
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.
- 4d ago First seen · 124 lines · 1,399 tokens per session scan A f17a067856d4
Wakeflow CLAUDE.md is an instructions file published in the GitHub repository GxFn/Wakeflow (5 stars, last pushed 10d ago), licensed MIT. It adds 1,399 tokens to every session, about $0.0070 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to Wakeflow AGENTS.md, differing in 26 lines, and is treated as a copy.
Other instructions, from other repositories
Citadel AGENTS.md
AGENTS.md instructions for SethGammon/Citadel, covering codex harness, what this is, key conventions, testing and review guidelines.
Citadel CLAUDE.md
Claude Code instructions for SethGammon/Citadel, covering claude harness, what this is, key conventions, testing and campaign design principles.
codex-image-context-runtime AGENTS.md
Instructions for shixinnt/codex-image-context-runtime, covering agents.md, public boundary, runtime contract and changes.
cool-workflow AGENTS.md
AGENTS.md instructions for coo1white/cool-workflow, covering cool workflow — autonomous development agent, quick index, role, hard rule — never push directly to main and iteration loop.
armorial AGENTS.md
AGENTS.md instructions for tetracoralla/armorial, covering armorial repository contract, product boundary and acceptance lanes.
AgentWorkspaceOS AGENTS.md
AGENTS.md instructions for zhangj012595-cloud/AgentWorkspaceOS, covering agent instructions, before making changes, public repository boundary, verification and shared coordination.