Borrowing it
Nothing to install: this file belongs to carloluisito/mindkeg-mcp. 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/carloluisito/mindkeg-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/carloluisito/mindkeg-mcpWrote 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/carloluisito/mindkeg-mcp/agents-md)<a href="https://agentmods.dev/instructions/carloluisito/mindkeg-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/carloluisito/mindkeg-mcp/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/carloluisito/mindkeg-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/carloluisito/mindkeg-mcp/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.03385 | $0.03385 |
| Opus 5 | $0.01692 | $0.01692 |
| Sonnet 5 | $0.00677 | $0.00677 |
| Haiku 4.5 | $0.00338 | $0.00338 |
Grade A, and why
mindkeg-mcp 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 10d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents
This file documents all available agents from personal Claude config (~/.claude-personal/agents/). No project-level agents exist in .claude/agents/. See CLAUDE.md for repo conventions all agents must follow.
Project Agent Registry
No project-level agents defined in .claude/agents/.
Personal Agent Registry
Source: ~/.claude-personal/agents/
architecture-design
Model: opus Purpose: Design system architecture, select tech stacks, define component boundaries, and produce authoritative architecture plans for new features or products. Scope: System-level decisions — service boundaries, data architecture, framework choices, scalability strategy, migration paths. Triggers: Designing a new major feature or product, introducing new services/subsystems, choosing frameworks or infrastructure, changing system shape (monolith to services, sync to async), before large feature execution. Constraints: Does NOT implement features, write code, or design UI. Produces the architecture plan that implementation must follow.
bug-fixer
Model: sonnet Purpose: Identify root cause of bugs and apply the smallest safe fix that corrects behavior without introducing unrelated changes. Scope: Reported bugs, failing tests, incorrect behavior, production issues, flaky/intermittent failures. Triggers: Bug reported, test failing, behavior incorrect or inconsistent, production/staging issue, flaky failures. Constraints: No unrelated refactors, no style cleanups, no new features, no architecture changes, no dependency updates unless required for the fix. Must include regression test.
bug-investigator
Model: opus Purpose: Forensic analysis and root cause identification for bugs. Traces execution paths, analyzes state mutations, identifies race conditions, isolates minimal failing conditions. Scope: Investigation only — unclear or intermittent bug behavior, production incidents, multi-layer failures, flaky tests, confusing logs, performance regressions, data corruption. Triggers: Bug behavior is unclear or intermittent, production incidents, failures spanning multiple layers, nondeterministic tests, confusing errors, performance regressions, data state issues. Constraints: NEVER applies fixes, modifies code, refactors, or adds features. Investigation and reporting only. Every claim requires evidence.
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.
- 10d ago First seen · 224 lines · 3,385 tokens per session scan A 6d461899560a
mindkeg-mcp AGENTS.md is an instructions file published in the GitHub repository carloluisito/mindkeg-mcp (11 stars, last pushed 4mo ago), licensed MIT. It adds 3,385 tokens to every session, about $0.0169 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).
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.
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.