Borrowing it
Nothing to install: this file belongs to karmacircleCommunity/KarmaCircle. 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/karmacircleCommunity/KarmaCircle/main/AGENTS.mdgit clone --depth 1 https://github.com/karmacircleCommunity/KarmaCircleWrote 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/karmacirclecommunity/karmacircle/agents-md)<a href="https://agentmods.dev/instructions/karmacirclecommunity/karmacircle/agents-md"><img src="https://agentmods.dev/badge/instructions/karmacirclecommunity/karmacircle/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.01466 | $0.01466 |
| Opus 5 | $0.00733 | $0.00733 |
| Sonnet 5 | $0.00293 | $0.00293 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
KarmaCircle 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 8d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentic workflow
- This is a monorepo:
apps/web(frontend,karmacircle-frontend) andapps/api(backend,karmacircle-api). Read docs/specs/README.md for the frontend's master map, and apps/api/docs/specs/README.md for the backend's — each covers only its own app. - Read docs/specs/known-issues.md (frontend) and/or apps/api/docs/specs/known-issues.md (backend) before touching any area either flags — duplicated implementations, dead code, unrouted pages, and validation that doesn't actually block submission are all cataloged there so you don't rediscover them the hard way.
- For anything touching a route path, method, or request/response shape, read apps/api/docs/specs/api-contract.md first — it cross-references every backend route against exactly what the frontend calls, and documents where they currently disagree. Don't assume a route "just works" for the frontend without checking that file.
- There is no
PRODUCT_SPEC.md, task-spec template, or Definition-of-Done doc in this repo yet — each app'sdocs/specs/is the closest thing to a source of truth today. - There is one graphify knowledge graph at graphify-out/, covering both apps' code (AST) plus
docs/specs/and the top-level docs. Readgraphify-out/GRAPH_REPORT.mdbefore answering architecture questions — see the "graphify" section inCLAUDE.mdfor how to query and keep it updated. - Test tooling differs per app:
apps/webhas no unit-test runner, onlycypress:run/cypress:open(one minimal e2e spec).apps/apihas Jest + Supertest (npm test), but only theauth,events,products, andusersmodules currently have test files —organizations,directory,payments, andreportsare untested. Don't claim something is "tested" without running it through the relevant tooling or manually verifying.
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.
- 8d ago First seen · 40 lines · 1,466 tokens per session scan A 63a1d0464781
KarmaCircle AGENTS.md is an instructions file published in the GitHub repository karmacircleCommunity/KarmaCircle (396 stars, last pushed 2d ago), licensed MIT. It adds 1,466 tokens to every session, about $0.0073 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-30.
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.