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/tomkyle/branched-openspec/agents-mdgit clone --depth 1 https://github.com/tomkyle/branched-openspecWhat 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.00968 | $0.00968 |
| Opus 5 | $0.00484 | $0.00484 |
| Sonnet 5 | $0.00194 | $0.00194 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
branched-openspec 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 2d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/contains the source YAML files (single source of truth for prompts).prompts/holds generated Codex/OpenCode prompt markdown files.commands/contains generated Gemini extension TOML files.scripts/build.jsis the Node.js build script that generates distribution files from source.Makefileprovides build and install/uninstall helpers for Codex, OpenCode, and Gemini CLIs.gemini-extension.jsonis the Gemini extension manifest.package.jsonmanages Node.js dependencies and npm scripts..markdownlint.jsonconfigures the markdown linter for CI validation.
Build, Test, and Development Commands
pnpm installornpm installinstalls Node.js dependencies (js-yaml, chokidar-cli, etc.).npm run buildormake buildor./scripts/build.jsgenerates prompts/.md and commands/.toml from src/*.yaml.npm run watchruns in watch mode, automatically rebuilding when src/*.yaml files change.npm run watch:srcrebuilds when src/**/*.yaml changes.npm run watch:tomlvalidates commands/**/*.toml on change.npm run watch:mdlints prompts/*.md on change.npm run lintruns all lint checks (TOML parse validation + Markdown linting).npm run lint:tomlvalidates TOML in commands/*.toml via scripts/validate-toml.js.npm run lint:mdlints prompts/*.md with markdownlint.make helpshows available Makefile targets with descriptions.make codexsymlinks prompt files into~/.codex/prompts(requirescodexCLI).make opencodesymlinks prompt files into~/.config/opencode/commands/(requiresopencodeCLI).make geminiinstalls the Gemini extension (requiresgeminiCLI).make installruns both codex and gemini installers.make uninstallremoves Codex/OpenCode symlinks and uninstalls the Gemini extension.act -W .github/workflows/ci.ymlruns the CI workflow locally (requiresactand Docker).
Coding Style & Naming Conventions
- Edit source files in
src/*.yamlonly; never edit generated files inprompts/orcommands/directly. - Use YAML formatting in
src/, Markdown in generatedprompts/, and TOML in generatedcommands/. - Keep filenames descriptive and aligned with the prompt name (
branched-openspec). - Prefer concise, imperative wording in prompt instructions.
- Follow JSDoc conventions in
scripts/build.jsfor function documentation.
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.
- 2d ago First seen · 60 lines · 968 tokens per session scan A 4cd2c6002617
branched-openspec AGENTS.md is an instructions file published in the GitHub repository tomkyle/branched-openspec (3 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 968 tokens to every session, about $0.0048 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
gemini-extension GEMINI.md
Instructions for OilpriceAPI/gemini-extension, covering oilpriceapi grounding instructions, ground product answers, route data requests, present data precisely and recover from failures.
gemini-beads GEMINI.md
Instructions for thoreinstein/gemini-beads, covering beads - persistent task memory, core mandates for beads, when to use beads (bd), session protocol (the workflow) and key commands.
gemini-time-injector GEMINI.md
Gemini CLI instructions for kongyo2/gemini-time-injector, covering time-injector extension and how to use this information.
gemini-redteam GEMINI.md
Gemini CLI instructions for Baba01hacker666/gemini-redteam, covering red team gem — security research context, baseline behavior, domain coverage, output style and response quality standard.
obsidian-mind CLAUDE.md
Claude Code instructions for breferrari/obsidian-mind, covering obsidian mind, skills & capabilities, custom slash commands, vault structure and obsidian cli.
switchback-running CLAUDE.md
Instructions for rlacombe/switchback-running, covering ultrarunning training companion, constitution, athlete data, training philosophy and core principles.