Borrowing it
Nothing to install: this file belongs to sturlese/stigmergy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sturlese/stigmergy/main/AGENTS.mdgit clone --depth 1 https://github.com/sturlese/stigmergyWrote 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/sturlese/stigmergy/agents-md)<a href="https://agentmods.dev/instructions/sturlese/stigmergy/agents-md"><img src="https://agentmods.dev/badge/instructions/sturlese/stigmergy/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.00372 | $0.00372 |
| Opus 5 | $0.00186 | $0.00186 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
stigmergy 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 6d 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.
What it actually says
Stigmergy — Codex instructions
Read CLAUDE.md before beginning substantive work. It is the shared project doctrine: orientation, invariants, working rules, testing doctrine, and completion requirements. Do not duplicate or change it for Codex-specific configuration.
The Stigmergy operating procedures are versioned under .claude/skills/. Codex does not discover that directory automatically, so read the matching SKILL.md directly when its trigger applies:
land-a-changefor an issue, defect, or feature.validate-deploymentafter a deploy, a cross-subsystem release, or when deployment health needs evidence.
When those procedures refer to a Claude squad:* workflow, use the installed Build Squad Codex plugin equivalent:
| Claude workflow | Codex skill |
|---|---|
squad:fix |
$build-squad:squad-fix |
squad:define |
$build-squad:squad-define |
squad:build |
$build-squad:squad-build |
squad:refactor |
$build-squad:squad-refactor |
squad:review |
$build-squad:squad-review |
squad:semantic-architecture |
$build-squad:squad-semantic-architecture |
squad:breaking-change |
$build-squad:squad-breaking-change |
squad:final-validation |
$build-squad:squad-final-validation |
Do not edit .claude/ for Codex-specific work.
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.
- 6d ago First seen · 24 lines · 372 tokens per session scan A 1a45e2f691b8
stigmergy AGENTS.md is an instructions file published in the GitHub repository sturlese/stigmergy (9 stars, last pushed 11d ago), licensed Apache-2.0. It adds 372 tokens to every session, about $0.0019 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.