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/originprotocol/origin-dollar/agents-mdgit clone --depth 1 https://github.com/OriginProtocol/origin-dollarWrote 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/originprotocol/origin-dollar/agents-md)<a href="https://agentmods.dev/instructions/originprotocol/origin-dollar/agents-md"><img src="https://agentmods.dev/badge/instructions/originprotocol/origin-dollar/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.01089 | $0.01089 |
| Opus 5 | $0.00544 | $0.00544 |
| Sonnet 5 | $0.00218 | $0.00218 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
origin-dollar 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 today.
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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Instructions
- See CLAUDE.md for repo commands, architecture, and workflow details.
- All smart contract work happens in
contracts/. Run repo commands from/Users/nicholasaddison/Documents/Origin/workspaces/origin-dollar/contracts. - After making code changes, run Prettier before finishing.
- For JS edits under
contracts/, runpnpm prettier:js. - For Solidity edits under
contracts/, runpnpm prettier:sol. - If both JS and Solidity files changed, run both commands.
- Prefer the smallest relevant verification after edits.
- Do not reformat or modify unrelated files just to satisfy style.
- Do not fix unrelated failing tests or lint issues unless explicitly asked.
Skills
A skill is a set of local instructions to follow that is stored in a SKILL.md file. Below is the list of skills that can be used. Each entry includes a name, description, and file path so you can open the source for full instructions when using a specific skill.
Available skills
- skill-creator: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations. (file: /Users/clement/.codex/skills/.system/skill-creator/SKILL.md)
- skill-installer: Install Codex skills into
$CODEX_HOME/skillsfrom a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos). (file: /Users/clement/.codex/skills/.system/skill-installer/SKILL.md) - commit: Handle git commits with auto-staging, targeted pre-commit formatting, and Conventional Commit messages. Use when the user asks to commit changes, save changes in git, or similar commit requests. (file: /Users/clement/Documents/Travail/Origin/2-SC/origin-dollar-foundry/.codex/skills/commit/SKILL.md)
- unit-test: Generate Foundry unit tests for a contract using this repository's conventions, structure, and naming. Use when the user asks for unit tests, Foundry tests, concrete tests, fuzz tests, or to port Hardhat tests into Foundry unit tests. (file: /Users/clement/Documents/Travail/Origin/2-SC/origin-dollar-foundry/.codex/skills/unit-test/SKILL.md)
- fork-test: Generate Foundry fork tests for contracts that need real on-chain integration coverage. Use when the user asks for fork tests, mainnet or chain fork coverage, integration tests against live protocol state, or to port Hardhat fork tests into Foundry. (file: /Users/clement/Documents/Travail/Origin/2-SC/origin-dollar-foundry/.codex/skills/fork-test/SKILL.md)
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.
- today First seen · 41 lines · 1,089 tokens per session scan A 0a15f1e78c84
origin-dollar AGENTS.md is an instructions file published in the GitHub repository OriginProtocol/origin-dollar (151 stars, last pushed yesterday), licensed MIT. It adds 1,089 tokens to every session, about $0.0054 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-09-04.
Other instructions, from other repositories
WAIaaS CLAUDE.md
Instructions for waiaas/WAIaaS, covering waiaas project rules, language, communication, schema & type system and database.
krait CLAUDE.md
Instructions for ZealynxSecurity/krait, covering claude.md, project shape, common commands, run a single test file or test by name and cli architecture (src/).
ponscli CLAUDE.md
Claude Code instructions for mesutgulecen/ponscli, covering ponscli, the rule that matters most, layout, verifying a change and things that will bite.
coingecko-mcp-server AGENTS.md
AGENTS.md instructions for cyanheads/coingecko-mcp-server, covering developer protocol, what's next?, core rules, patterns and tool.
coingecko-mcp-server CLAUDE.md
Claude Code instructions for cyanheads/coingecko-mcp-server, covering developer protocol, what's next?, core rules, patterns and tool.
quantum-shield AGENTS.md
AGENTS.md instructions for kota1026/quantum-shield, covering agents.md - quantum shield project, project overview, core components, allowed actions and file operations.