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/alphaelements/handoff-mcp/agents-mdgit clone --depth 1 https://github.com/alphaelements/handoff-mcpWhat 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.00820 | $0.00820 |
| Opus 5 | $0.00410 | $0.00410 |
| Sonnet 5 | $0.00164 | $0.00164 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
handoff-mcp AGENTS.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 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
handoff-mcp repository guidance
Scope and safety
- Work in the current repository and preserve unrelated user changes.
- Do not push, publish, deploy, or commit directly to
mainormaster. - Do not edit
.handoff/files directly. Use the Handoff MCP tools for task, session, document, and memory state. - Treat write, network, credential, migration, and destructive operations as requiring the applicable Codex approval or explicit user authorization.
Session handoff
This repository uses Handoff MCP for session continuity.
- At session start, call
handoff_load_context. If it returnssession_guidance, establish an active session withhandoff_save_context(session_status: "active")before work begins. - Track implementation work with
handoff_update_task; check each verified done criterion withhandoff_check_criterionbefore moving a task todone. - At session end, save a concise summary, decisions, blockers, context pointers, related task IDs, and concrete next-step suggestions.
Repository workflow
-
Rust commands must source
scripts/cargo-env.shfirst. Use it for builds, tests, formatting, clippy, audit, and cargo-deny checks. -
Run focused checks for the files changed, then the relevant release checks:
. scripts/cargo-env.sh && cargo fmt --all -- --check . scripts/cargo-env.sh && cargo clippy --all-targets -- -D warnings . scripts/cargo-env.sh && cargo test npm run test:js ./scripts/sync-workflow-inline.sh --check ./scripts/sync-plugin-skills.sh --check ./scripts/sync-plugin-version.sh --check -
When the Codex CLI is installed, also run
npm run test:codex-plugin. It installs the plugin into an empty local Codex profile and verifies the installed package contents. -
When changing the package version, keep
package.json,Cargo.toml, the Claude plugin manifests, andplugins/handoff-task-loop-codex/.codex-plugin/plugin.jsonin sync. The existing version-sync script covers the Claude manifests; update the Codex manifest deliberately and verify it too. -
When changing shared skills under
skills/, run./scripts/sync-plugin-skills.shso the marketplace-servedplugin/skills/copy remains synchronized. -
Validate a Codex plugin and each changed Codex skill before release. Install it from the repository marketplace and verify the installed cache rather than only validating source files.
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 · 77 lines · 820 tokens per session scan A 43b8f73d80b3
handoff-mcp AGENTS.md is an instructions file published in the GitHub repository alphaelements/handoff-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 820 tokens to every session, about $0.0041 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.