RedAmon is an AI framework that connects reconnaissance, exploitation, and post-exploitation activities into an automated security-testing pipeline, while organizing findings and proposing code fixes. It is for authorized penetration testing, security research, and education. The catalogue entries provide skills and instructions for working with the framework.
Borrowing it
Nothing to install: this file belongs to samugit83/redamon. 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/samugit83/redamon/master/AGENTS.mdgit clone --depth 1 https://github.com/samugit83/redamonWrote 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/samugit83/redamon/agents-md)<a href="https://agentmods.dev/instructions/samugit83/redamon/agents-md"><img src="https://agentmods.dev/badge/instructions/samugit83/redamon/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/samugit83/redamon/agents-md"><img src="https://agentmods.dev/badge/instructions/samugit83/redamon/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.02716 | $0.02716 |
| Opus 5.5 | $0.01086 | $0.01086 |
| Sonnet 5.5 | $0.00543 | $0.00543 |
| Haiku 4.5 | $0.00272 | $0.00272 |
Grade A, and why
redamon 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 12d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RedAmon - Agent Ruleset (Repository Root)
Skills: on-demand rulesets live in
skills/. The full list is the SKILLS CATALOGUE at the bottom of this file. The table directly below is generated bysync.shfrom each skill's frontmatter - never hand-edit it.This ruleset system is documented in
docs/readmes/skills_management/SKILLS_MANAGEMENT.md.
Auto-invoke Skills
When performing these actions, ALWAYS invoke the corresponding skill FIRST:
| Action | Skill |
|---|---|
| Adding a node label, relationship, or property to the graph schema | graph-db-writes |
| Adding or editing a test file in any section | redamon-testing |
| Changing how a triage score, review or verdict is computed or written | priority-board-triage |
| Changing how plugin services, networks or the plugins overlay are started by redamon.sh or compose | plugin-platform |
| Changing test tiers, conftest.py, pytest.ini, or the runner in redamon.sh | redamon-testing |
| Checking or ratcheting a coverage floor | redamon-testing |
| Editing the Priority Board, the triage graph mixin, or the MCP triage tools | priority-board-triage |
| Editing the plugin platform: the plugins lib or routes, the plugin runner, or the Gateway | plugin-platform |
| Investigating a red, skipped or xfailed test | redamon-testing |
| Writing to the Neo4j graph or editing a graph_db mixin | graph-db-writes |
CRITICAL RULES - NON-NEGOTIABLE
- NEVER commit real-world target data - live hostnames, IPs, scan output,
recon results, captured traffic, or credentials - in code, fixtures, tests,
issues, or PRs. See
CONTRIBUTING.md-> "Legal and Ethical Responsibilities". - NEVER validate a change by running
pyteston the host. The Python gate runs each section INSIDE its Docker image (redamon-agent,redamon-recon, ...) via./redamon.sh test/./agentic/run_tests.sh; host pytest sees the wrong dependency set and mis-collects. The unit tier must stay 100% green.
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.
- 12d ago Changed · +8 lines · +185 tokens per session 9d8e050e9fc2
- 26d ago Changed · +9 lines · +208 tokens per session af9cc9ad02b2
- 1mo ago Changed · +1 lines · +47 tokens per session b7defb3308cb
- 1mo ago First seen · 155 lines · 2,276 tokens per session scan A b1b801a1b599
redamon AGENTS.md is an instructions file published in the GitHub repository samugit83/redamon (3,221 stars, last pushed 5d ago), licensed MIT. It adds 2,716 tokens to every session, about $0.0109 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-30.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.