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/ashfulcra/fulcra-tools/agents-mdgit clone --depth 1 https://github.com/ashfulcra/fulcra-toolsWrote 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/ashfulcra/fulcra-tools/agents-md)<a href="https://agentmods.dev/instructions/ashfulcra/fulcra-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/ashfulcra/fulcra-tools/agents-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.1 | $0.27748 | $0.27748 |
| Opus 5 | $0.13874 | $0.13874 |
| Sonnet 5 | $0.05550 | $0.05550 |
| Haiku 4.5 | $0.02775 | $0.02775 |
Grade A, and why
fulcra-tools AGENTS.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
self-contained piece of evidence (a curl, a traceback). Ten lines. How it starts
The opening of the file, as written. The whole thing — 1,505 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fulcra Tools — agent guide
Your entry point to this repo. Fulcra helps agents know their user, know
what's happening in their user's world, work with their user's other agents,
and become more helpful over time — the packages here are working examples of
all four. This file covers the non-obvious environment and the conventions
you can't infer from the source; the README.md tells the
top-level story (what each package is, how to install the pieces) and this
file does not repeat it.
This file is a ship-gate artifact. Every PR that changes agent-facing
behavior — CLI verbs, skills, conventions, environment requirements, review
rules — MUST update this file in the same PR. Reviewers: treat a stale
AGENTS.md as a blocking finding. If your change doesn't alter what an agent
needs to know, say so in the PR body ("AGENTS.md: no change needed").
No one-off fixes on coordination or continuity surfaces (operator law,
2026-08-14; earned by twelve strict-consumer incidents,
OUTPUT-CONTRACT.md). Root-cause every
incident and fix it upstream at the surface that produced it, not with a
defensive patch at the consumer. The models reading these surfaces are smart;
what they need from us is surfaces that are durable.
Where to start
Zero state — never installed coord-engine, or joining from a fresh / remote /
sandboxed host? Start at
docs/coord/GET-ON-THE-BUS.md — install → auth →
(remote egress) → team bootstrap from zero → join. The probe grid below assumes the
engine is installed and a <team> exists; if coord-engine is command not found
or you have no team yet, the grid can't help you — the quickstart is the entry.
Already on the bus? Run the probes top to bottom, then jump to the layer you're touching. First failing probe is where your setup gap is.
| Probe / question | Command | Passes when | Where to go |
|---|---|---|---|
| Engine + auth usable? | coord-engine doctor <team> |
exits 0 — tooling present, store reachable | never installed / command not found / no team yet → docs/coord/GET-ON-THE-BUS.md (install → auth → bootstrap → join). Otherwise fix the reported gap (auth: fulcra auth login; missing/old coord-engine: reinstall) |
| On the bus? | coord-engine queue <team> --agent <you> (bus v3; raw get-records if the engine predates v1.7.0), then coord-engine briefing <team> --agent <you> for the durable board |
queue read completes — and if it stages a queue-delivery token (cursor schema v2), the probe passes only after every record is classified and queue commit succeeds; briefing prints your identity, role inboxes, reviews owed |
Coordinate on the bus — events are the wake surface, the fold is the full picture |
| Two identities joined end to end? | coord-engine acceptance pair <team> --agent <A> --peer <B> |
every timed hop prints HOP N PASS and the command ends PASS pair A<->B; any bad nonce, missing checkpoint, stale resume, degraded queue, or failed write exits at FAILED AT HOP N with raw evidence |
GET-ON-THE-BUS.md |
| Own worktree? | git worktree list |
your cwd is a dedicated worktree, not a shared checkout (no conflict markers or foreign staged files) | Working tree — carve your own before committing |
| Touching Collect / the daemon? | — | — | The daemon (Collect) |
| Touching coord conventions? | — | — | Coordinate on the bus |
| Touching the platform surface? | — | — | Fulcra platform surface & records |
| Touching CI / hooks? | — | — | CI and workspace membership |
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 Changed · +37 lines · +756 tokens per session c9111ebe1107
- 5d ago First seen · 1,468 lines · 26,992 tokens per session scan A 64f95c15fb7c
fulcra-tools AGENTS.md is an instructions file published in the GitHub repository ashfulcra/fulcra-tools (10 stars, last pushed today), licensed MIT. It adds 27,748 tokens to every session, about $0.1387 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
cortex CLAUDE.md
Instructions for agentweave/cortex, covering cortex, project structure, key concepts, conventions and when editing skills.
magic-compact AGENTS.md
Instructions for aerovato/magic-compact, covering magic compact — agent instructions, with npm, with bun and install opencode plugin.
universal-remote-control AGENTS.md
AGENTS.md instructions for sidkandan/universal-remote-control, covering urc — cli-to-cli communication & rc bridge, rc bridge system, available mcp tools, urc-coordination (pane communication — 11 tools) and urc-teams (dormant — removed from .mcp.json).
universal-remote-control CLAUDE.md
Claude Code instructions for sidkandan/universal-remote-control, covering urc — rc bridge + cli-to-cli communication, quick start, development rules, architecture (v3) and communication strategy.
universal-remote-control GEMINI.md
Gemini CLI instructions for sidkandan/universal-remote-control, covering urc — cli-to-cli communication & rc bridge, what this is, rc bridge, available mcp tools (urccoordination — 11 tools) and turn completion.
ainl-cortex CLAUDE.md
Claude Code instructions for sbhooley/ainl-cortex, covering ainl plugin instructions for claude code, plugin setup (for new users), one command (all platforms), what happens automatically (no user steps) and windows install playbook (for agents).