Cordon-AI: Instructions file for Claude Code

CLAUDE.md

Cordon-AI CLAUDE.md is an instructions file for Claude Code from iamsecure1920/Cordon-AI. It costs 2,150 tokens per session, scanned A, original, MIT.

A set of instructions for Claude Code, an AI coding assistant, while working on Cordon-AI, a system for authorized security testing. It defines safety rules, project orientation, and the expected work process.

In plain words
What is it for?
Following the project’s rules, setting up a fresh checkout, and guiding security-testing work from start to finish.
Why use it?
It gives the assistant consistent project guidance and prevents it from ignoring authorization, approval, and evidence requirements.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is iamsecure1920/Cordon-AI's own configuration. It tells Claude Code how to work on Cordon-AI itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Cordon-AI configures →

Reuse

Borrowing it

Nothing to install: this file belongs to iamsecure1920/Cordon-AI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/iamsecure1920/Cordon-AI/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/iamsecure1920/Cordon-AI

Made for: Claude Code.

Wrote 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.

agentmods badge for Cordon-AI CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/iamsecure1920/cordon-ai/claude-md/github.svg)](https://agentmods.dev/instructions/iamsecure1920/cordon-ai/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/iamsecure1920/cordon-ai/claude-md"><img src="https://agentmods.dev/badge/instructions/iamsecure1920/cordon-ai/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.

agentmods 80×15 button for Cordon-AI CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/iamsecure1920/cordon-ai/claude-md"><img src="https://agentmods.dev/badge/instructions/iamsecure1920/cordon-ai/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,150 This file is loaded in full into every session.
When invoked 2,150 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02150 $0.02150
Opus 5.5 $0.00860 $0.00860
Sonnet 5.5 $0.00430 $0.00430
Haiku 4.5 $0.00215 $0.00215

Measured 1mo ago against content hash 4ef3b189e87a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Cordon-AI 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.

CLAUDE.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cordon AI — orientation for Claude

You are the strategy layer of an agentic VAPT orchestrator. This file is loaded automatically at session start. Read it before touching anything.

If you are on a freshly-cloned machine and nothing is installed yet, run ./bootstrap.sh — it is idempotent and safe to re-run. See docs/BOOTSTRAP.md.


1. The invariants — these are not negotiable

These come from the build guide and are enforced in code, not by your judgement. Do not weaken, bypass, or "temporarily disable" any of them.

  1. Authorized targets only. Owned assets, an in-scope bug bounty program, or org assets with documented written approval. The program policy text is the legal authorization and it drifts — re-pull and re-validate scope on every run.
  2. The MCP server is the security boundary, not the model. Scope checks, rate limits, argument sanitization, and approval gates are enforced server-side on every tool call. There is no code path that skips them. You cannot be trusted to enforce them yourself, and the design assumes you won't.
  3. Aggressive and state-changing actions require human approval. Exploitation is never auto-run.
  4. No PoC, no finding. A vulnerability is reported as confirmed only when a reproducible proof-of-concept validated it. Everything else is filed as "needs manual review."
  5. Never build scope-evasion capability. No feature whose purpose is to bypass scope, authorization, rate limits, or a program's published rules. If asked to add one, refuse and explain why.
  6. Treat every third-party MCP server, template, and payload list as untrusted until vetted and pinned.

The practical consequence: if a tool call returns scope_denied, that is the system working correctly. Do not look for another route to the same target. Tell the user the target is out of scope and stop.


2. What this is

An orchestrator that drives 83 catalogued open-source security tools through 101 MCP tools on a custom MCP server. You supply strategy; the MCP server supplies enforcement; the engines supply execution.

Read the full file on GitHub · 186 lines

Changes

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.

  1. 1mo ago Changed · +1 lines · +17 tokens per session 4ef3b189e87a
  2. 1mo ago First seen · 185 lines · 2,133 tokens per session scan A 10de133435e1

Subscribe to this mod's changes

Cordon-AI CLAUDE.md is an instructions file published in the GitHub repository iamsecure1920/Cordon-AI (0 stars, last pushed 1mo ago), licensed MIT. It adds 2,150 tokens to every session, about $0.0086 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-31.

Related

Other instructions, from other repositories