Borrowing it
Nothing to install: this file belongs to nick-pape/grackle. 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/nick-pape/grackle/main/CLAUDE.mdgit clone --depth 1 https://github.com/nick-pape/grackleWrote 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/nick-pape/grackle/claude-md)<a href="https://agentmods.dev/instructions/nick-pape/grackle/claude-md"><img src="https://agentmods.dev/badge/instructions/nick-pape/grackle/claude-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/nick-pape/grackle/claude-md"><img src="https://agentmods.dev/badge/instructions/nick-pape/grackle/claude-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.06739 | $0.06739 |
| Opus 5.5 | $0.02696 | $0.02696 |
| Sonnet 5.5 | $0.01348 | $0.01348 |
| Haiku 4.5 | $0.00674 | $0.00674 |
Grade A, and why
grackle CLAUDE.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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grackle Development Guidelines
Self-Updating Documentation
When you encounter unexpected issues, workarounds, or non-obvious behavior (CI quirks, tooling gotchas, environment-specific problems), update this CLAUDE.md with the finding so future sessions don't repeat the investigation. Add the note to the most relevant existing section, or create a new one if needed.
Package READMEs
Each package under packages/ has a README.md that is published to npm. When you change a package's public behavior (new commands, renamed options, new MCP tools, new API methods, changed configuration, etc.), update that package's README to match. Do not let READMEs drift out of sync with the code.
- CLI (
packages/cli/README.md): documents every command, subcommand, and flag. Update when adding/removing/renaming commands or options. - MCP (
packages/mcp/README.md): documents every MCP tool with parameters. Update when adding/removing/renaming tools. - Knowledge Core (
packages/knowledge-core/README.md): detailed API reference. Update when the public API changes. - All other packages: concise overviews. Update if the package's purpose, key concepts, or usage instructions change.
Do not update the root README.md as part of this process — it is a separate marketing/overview document maintained independently.
Environment Variables
The root .env.example documents every supported environment variable with defaults and descriptions. When you add, remove, or rename a process.env read, update .env.example to match.
Git Workflow
- Never push directly to main. All changes must go through a pull request. Always create a feature branch and open a PR — never commit and push to
main. - Never rebase or force-push. To sync with
main, first rungit fetch originand then usegit merge origin/maininstead ofgit rebase. Rebasing published branches rewrites history and typically requires a force-push, which we do not allow. - Never merge PRs unless the user explicitly tells you to merge. Other agents may be coordinating merge order.
- Branch naming:
<github-username>/<issue>-<feature>when working on a GitHub issue (where<issue>is the numeric issue id, e.g.,nick-pape/149-agent-subtask-creation), or<github-username>/<feature>when there's no issue (e.g.,nick-pape/fix-typo-in-readme).
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 · 289 lines · 6,739 tokens per session scan A d751a97a6e60
grackle CLAUDE.md is an instructions file published in the GitHub repository nick-pape/grackle (22 stars, last pushed 4mo ago), licensed MIT. It adds 6,739 tokens to every session, about $0.0270 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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.