Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/rafael-adcp/kraken/agents-mdgit clone --depth 1 https://github.com/rafael-adcp/krakenWrote 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/rafael-adcp/kraken/agents-md)<a href="https://agentmods.dev/instructions/rafael-adcp/kraken/agents-md"><img src="https://agentmods.dev/badge/instructions/rafael-adcp/kraken/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.01525 | $0.01525 |
| Opus 5 | $0.00763 | $0.00763 |
| Sonnet 5 | $0.00305 | $0.00305 |
| Haiku 4.5 | $0.00153 | $0.00153 |
Grade A, and why
kraken 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 5d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — running as a kraken tentacle
This file lets an agents.md-aware agent CLI (GitHub Copilot CLI, and others that
auto-load AGENTS.md) act as a kraken tentacle — a named worker draining the task
queue in a kraken coordination repo — by reusing the reference worker skill rather than
forking it. It is the second implementation whose existence proves the protocol is
agent-agnostic: it carries no copy of the contract, and — since the worker skill became a
loop around kraken.py next-action — no deltas either.
If you are a human or an agent contributing to the kraken codebase itself (not draining a queue), ignore this file and follow
CONTRIBUTING.md.
Your operating contract — read these, then follow them
PROTOCOL.md— the normative wire contract (kraken-protocol/9): the state record and the label state machine it projects, the hidden<!-- kraken {...} -->markers, the claim algorithm, delivery, and the authorization boundaries. Agent-agnostic already.skills/unleash/SKILL.md— how a worker executes that contract. Read it in full and follow it. Every transition runs through the bundledskills/unleash/kraken.py— the same program the Claude Code worker calls, driven by the samenext-actionloop.skills/unleash/DELIVERY.md— the delivery conventions SKILL.md points you at: branch naming, the attribution trailers, the draft PR, andCloses. It names yourCo-Authored-Byidentity (Co-Authored-By: GitHub Copilot <[email protected]>) alongside Claude Code's.
You are invoked with the same three required arguments SKILL.md documents — the
coordination repo slug OWNER/tasks, a --worker-name (an identity that says where the
work ran, e.g. kraken-copilot-1), and a --project (only take project:<name> tasks).
Why there are no deltas any more
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.
- 5d ago First seen · 103 lines · 1,525 tokens per session scan A f52250f27bc1
kraken AGENTS.md is an instructions file published in the GitHub repository rafael-adcp/kraken (4 stars, last pushed 1mo ago), licensed MIT. It adds 1,525 tokens to every session, about $0.0076 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
ai-literacy-superpowers copilot-instructions.md
Copilot instructions for Habitat-Thinking/ai-literacy-superpowers, covering project conventions and constraints, stack, naming, file structure and error handling.
matilha-skills GEMINI.md
Instructions for danilods/matilha-skills, covering matilha — cognitive + methodological harness, how this loads in gemini cli, phases (0-70), companion detection and tool mapping.
AI-Prompt-Guide-MCP CLAUDE.md
Claude Code instructions for Blakeem/AI-Prompt-Guide-MCP, a project described as: Deprecated. MCP server and Claude Code plugin with task driven agent orchestration workflows, guides, markdown knowledge graphs, with intelligent context injection.
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.
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.