Borrowing it
Nothing to install: this file belongs to rolecraft-sh/rolecraft. 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/rolecraft-sh/rolecraft/main/AGENTS.mdgit clone --depth 1 https://github.com/rolecraft-sh/rolecraftWrote 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/rolecraft-sh/rolecraft/agents-md)<a href="https://agentmods.dev/instructions/rolecraft-sh/rolecraft/agents-md"><img src="https://agentmods.dev/badge/instructions/rolecraft-sh/rolecraft/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/rolecraft-sh/rolecraft/agents-md"><img src="https://agentmods.dev/badge/instructions/rolecraft-sh/rolecraft/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00845 | $0.00845 |
| Opus 5.5 | $0.00338 | $0.00338 |
| Sonnet 5.5 | $0.00169 | $0.00169 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
rolecraft 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rolecraft — Development Guidelines
📖 Agent discovery paths are in
docs/agents.md
⚠️ STARTUP CHECKLIST (read before every task)
git checkout main && git pull— start from latest maingit checkout -b feat/my-featureorfix/my-bug— create branch- Do all work on the feature branch (never on main)
npm run lint— check syntax before pushingnpm test— run tests- Never leave changes that break tests
- Write tests for new features
- Update docs (README, docs/) when needed
- Test
--dry-runflag if the feature supports it git add ... && git commit -m "type: short description"— title only, no bodygit push -u origin <branch>— pushgh pr create— open PR with short one-sentence body- Before merging, wait for all GitHub Actions checks to pass (
gh run watchor check PR status). Never merge while checks are running.
Workflow
- Before starting any task, ensure you're on
mainwith latest changes (git checkout main && git pull), then create a new branch specific to the task (git checkout -b feat/my-featureorfix/my-bug) - Complete all work on the feature branch
- After completing the work, run
npm run lintand the tests:node --test --test-concurrency=1 - Never leave changes that break tests
- Write tests for new features
- Update documentation (README, docs/) when needed
- Test the
--dry-runflag if the feature supports it - After tests pass, commit the changes (title only, no body), push the branch, and open a PR (one-sentence body)
- Before merging, wait for all GitHub Actions checks to pass (
gh run watchor check PR status). Never merge while checks are running.
Interaction rules
- Chat vs dev mode: Before writing any code, confirm whether the user wants development or just information. Ask: "Are you asking me to develop something or just asking for information?"
- Commit messages: Title only, no body. Example:
feat: add rolecraft mcp check command - PR body: One-sentence summary. Example: "Adds rolecraft mcp check command for npm update checks."
- Branch strategy: Always branch from latest main for any work that requires a commit, unless the user explicitly says otherwise.
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.
- 1mo ago First seen · 54 lines · 845 tokens per session scan A 5ac9595e7802
rolecraft AGENTS.md is an instructions file published in the GitHub repository rolecraft-sh/rolecraft (96 stars, last pushed 4d ago), licensed MIT. It adds 845 tokens to every session, about $0.0034 per session on Opus 5.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-30.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.