Borrowing it
Nothing to install: this file belongs to bitwise-media-group/skills. 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/bitwise-media-group/skills/main/AGENTS.mdgit clone --depth 1 https://github.com/bitwise-media-group/skillsWrote 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/bitwise-media-group/skills/agents-md)<a href="https://agentmods.dev/instructions/bitwise-media-group/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/bitwise-media-group/skills/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.01495 | $0.01495 |
| Opus 5 | $0.00747 | $0.00747 |
| Sonnet 5 | $0.00299 | $0.00299 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
skills 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bitwise skills — repository conventions
This repo is the bitwise skills/plugin marketplace: agent skills packaged as plugins, consumable by Claude Code,
OpenAI Codex CLI, Google Antigravity, and OpenCode. The global ~/.claude/CLAUDE.md (Conventional Commits, commit.sh
signing handoff) applies on top of this file.
CLAUDE.mdis a symlink to this file — always editAGENTS.md, neverCLAUDE.md.
Layout
- One plugin per directory under
plugins/<plugin>/. Skills are the canonical source of truth atplugins/<plugin>/skills/<skill-name>/SKILL.md— they exist exactly once; every distribution channel (Claude/Codex marketplaces,install.shsymlinks) points at this tree. - Evals live at
plugins/<plugin>/evals/<skill-name>/(triggers.json,evals.json, fixtures, and the committedresults.jsonthe sweeps write), not inside the skill directory, so installed skills stay lean. - Skill directory name must equal the frontmatter
name. - Skill names are globally namespaced by prefix (e.g.
terraform-style, notstyle) because Codex/Antigravity/OpenCode install skills into flat shared directories.
Dual manifests (Claude + Codex)
Every plugin carries two manifests; the repo carries two marketplace manifests:
| Consumer | Marketplace (repo root) | Plugin manifest |
|---|---|---|
| Claude Code | .claude-plugin/marketplace.json |
plugins/<n>/.claude-plugin/plugin.json |
| Codex CLI | .agents/plugins/marketplace.json |
plugins/<n>/.codex-plugin/plugin.json |
Rules:
- Versions stay in sync between the two plugin manifests (enforced by
evolve run checks). Codex requires strict semver. - Marketplace
sourcepaths are explicit and./-prefixed ("./plugins/terraform"). Do not use Claude'smetadata.pluginRoot— Codex fallback-reads Claude's manifest and resolves sources against the repo root. - Never add a
hooks/directory to a plugin. Codex default-discovershooks/hooks.jsonwith an incompatible schema.
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 · 98 lines · 1,495 tokens per session scan A 1907d2aaed3b
skills AGENTS.md is an instructions file published in the GitHub repository bitwise-media-group/skills (2 stars, last pushed yesterday), licensed MIT. It adds 1,495 tokens to every session, about $0.0075 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.