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/mateusoliveirab/clibridge/agents-mdgit clone --depth 1 https://github.com/mateusoliveirab/clibridgeWrote 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/mateusoliveirab/clibridge/agents-md)<a href="https://agentmods.dev/instructions/mateusoliveirab/clibridge/agents-md"><img src="https://agentmods.dev/badge/instructions/mateusoliveirab/clibridge/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 | $0.00544 | $0.00544 |
| Opus 5 | $0.00272 | $0.00272 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
clibridge 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 3d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clibridge contributor guide for coding agents
This is the tool-neutral entry point for AI contributors. Read this file before changing code; use CONTRIBUTING.md for the human workflow and docs/architecture.md for the system contract.
When present, also read agents.local.md. It defines the delegated maintainer operating mode and the routing policy for this checkout. It may authorize routine in-scope execution, but it never weakens the non-negotiable rules below or external platform protections.
Repository map
src/adapters/— provider-specific command construction and capability checks.src/broker/— routing, normalized errors, schema validation, and dispatch.src/daemon/— localhost-only control plane, SQLite ledger, approvals, SSE, and secret redaction.src/workflows/— workflow parsing, execution, and contribution policy.dashboard/— local operator console; it shares the daemon API and ledger.test/— offline node:test suite. Keep tests in this directory so the test command cannot accidentally collect nested worktrees.
Non-negotiable rules
- Never persist, log, or display raw credentials, tokens, prompts containing
secrets, or unredacted provider output. Use the redaction boundary in
src/daemon/redaction.ts. - Diagnostics and live validation must set
disableFallback: true; a fallback may hide an authentication, credit, or provider failure. - New provider behavior requires an adapter contract, capability validation, offline tests, and a documented live-validation command when a local binary is involved.
- New daemon mutations must retain project scoping, the approval gate for
risky work, ledger evidence, and the shared
src/daemon/client.tspath. - Do not publish packages, push branches, reset/clean Git state, or alter credentials without explicit user or maintainer authorization.
Required validation
Run npm run ci before opening a pull request. It runs TypeScript, the build,
the scoped offline test suite, and the dry-run smoke check. Run a relevant
live:validate:* command only when its provider binary
and credentials are available; never treat a skipped live check as proof.
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.
- 3d ago First seen · 48 lines · 544 tokens per session scan A 13d536c1263d
clibridge AGENTS.md is an instructions file published in the GitHub repository mateusoliveirab/clibridge (0 stars, last pushed 19d ago), licensed MIT. It adds 544 tokens to every session, about $0.0027 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
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).
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.
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.