Borrowing it
Nothing to install: this file belongs to CarbeneAI/Talon. 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/CarbeneAI/Talon/main/CLAUDE.mdgit clone --depth 1 https://github.com/CarbeneAI/TalonWrote 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/carbeneai/talon/claude-md)<a href="https://agentmods.dev/instructions/carbeneai/talon/claude-md"><img src="https://agentmods.dev/badge/instructions/carbeneai/talon/claude-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.00479 | $0.00479 |
| Opus 5 | $0.00239 | $0.00239 |
| Sonnet 5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
Talon 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 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Talon — Claude Code Project Instructions
Talon is a penetration testing workflow toolkit that connects Claude Code to a Kali Linux VM via SSH MCP.
MCP Server
The kali-ssh MCP server (configured in mcp-config.example.json) provides SSH access to your pentest VM. Copy the example config to ~/.claude/mcp.json and update with your host/username before use.
All shell commands in this project are intended to run on the remote Kali VM via the MCP connection, not locally.
Methodology
Follow the 5-phase pentest methodology defined in references/ and SKILL.md:
- Recon —
scripts/recon.sh <target-ip>for automated initial recon - Enumeration — Use
references/service-enum.mdfor per-service commands - Exploitation — Document and execute with searchsploit / metasploit / manual exploits
- Post-Exploitation — PrivEsc enumeration, credential harvesting, persistence
- Reporting — Use
references/report-template.mdfor structured findings
Obsidian Notes
Use templates in templates/ for engagement tracking:
templates/engagement.md— One per engagement, tracks all targets and credentialstemplates/target.md— One per machine, tracks recon, foothold, and PrivEsc
Key References
references/service-enum.md— Enumeration commands for 13 service typesreferences/report-template.md— OSCP-style report structuredocs/setup-kali.md— Kali VM setup guidedocs/ssh-access.md— Remote access methods (SSH tunnel, VPN, ngrok, Cloudflare)docs/usage.md— Example prompts and workflows
Security Rules
- Always confirm you have written authorization before testing any target
- Never store credentials, flags, or loot in this repository
- Keep scan output and results in local directories (gitignored)
- Rotate SSH keys regularly
Common Prompts
Ask Claude:
- "Run recon on [IP] using Kali"
- "Enumerate [service] on [IP]"
- "I have a shell as [user] — check for PrivEsc paths"
- "Generate a report for this engagement"
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 · 51 lines · 479 tokens per session scan A 2219aacc1f39
Talon CLAUDE.md is an instructions file published in the GitHub repository CarbeneAI/Talon (58 stars, last pushed 1mo ago), licensed MIT. It adds 479 tokens to every session, about $0.0024 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
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).
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.
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 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).
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.