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.
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 skills/samugit83/redamon/supply-chain-scannpx skills add samugit83/redamon --skill supply-chain-scangit 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/skills/samugit83/redamon/supply-chain-scan)<a href="https://agentmods.dev/skills/samugit83/redamon/supply-chain-scan"><img src="https://agentmods.dev/badge/skills/samugit83/redamon/supply-chain-scan.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.00115 | $0.00861 |
| Opus 5 | $0.00057 | $0.00430 |
| Sonnet 5 | $0.00023 | $0.00172 |
| Haiku 4.5 | $0.00012 | $0.00086 |
Grade A, and why
supply-chain-scan 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 6d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- Changing any of the three supply-chain layers (OSV, GuardDog, retire/trufflehog) or the offline database plumbing.
The supply_chain_common-must-be-bind-mounted rule is in the
AGENTS.md CRITICAL RULES; this skill is the
scanning behaviour.
Critical Rules
- NEVER assume the offline OSV database is populated. It is filled lazily,
per-ecosystem, only on the explicit
--download-offline-databasesstep - NOT on every scan and NOT at install time (scanners/supply_chain_common/osv_db_sync.py). A scan against an unsynced ecosystem must report it as missing, not crash. - NEVER
chmodthe OSV DB tighter than world-readable. The scanner runs hardened and non-root;osv_db_sync.pymakes the whole tree world-readable/traversable on purpose so the scanner can read it. Restricting it breaks offline scans silently. - NEVER erase an existing soft-error marker on a failed/invalid analysis. A
package the analyzer never actually inspected is recorded as a
soft_error(scanners/supply_chain_common/deep_recovery.py); invalid GuardDog output must be dropped, not allowed to overwrite those markers (regression fixed in commitc5cd6a16). - NEVER run the OSV binary without the
--offlinepairing. Offline mode uses the--offline --download-offline-databasespair; using one without the other either hits the network or reads an empty DB.
Layers
| Layer | Runner | Note |
|---|---|---|
| known vulns | osv_runner.py + osv_db_sync.py | offline OSV DB (named volume, lazily synced) |
| malicious behaviour | guarddog_runner.py | GuardDog heuristics; soft-errors via deep_recovery.py |
| dispatch | analyzer_dispatch.py | routes a package to the right analyzer |
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.
- 6d ago First seen · 72 lines · 115 tokens per session scan A 13883336d222
supply-chain-scan is a skill published in the GitHub repository samugit83/redamon (2,403 stars, last pushed 3d ago), licensed MIT. It adds 115 tokens to every session and 861 once invoked, about $0.0006 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 skills, from other repositories
workflow-orchestrator
Module Loop and Iteration Skill for orchestrating multi-phase penetration testing workflows. Use when coordinating sequential tool execution, managing dependencies between reconnaissance and vulnerability scanning modules, implementing adaptive fallback strategies, or managing workflow state across iterations.…
poc-validator
Proof-of-Concept (PoC) Validation Skill for security exploit verification. Use when validating exploitability of vulnerabilities, generating tailored payloads, executing exploits in sandboxed environments, or verifying successful exploitation (e.g., SQL injection, CVE exploitation, command injection). Triggers on…
Reconnaissance & OSINT Automation
Passive and active reconnaissance, subdomain enumeration, DNS analysis, technology fingerprinting, and OSINT data correlation for authorized security assessments.
tdd-agent
Autonomous test-driven development agent that writes code to make tests pass.
penetration-testing-expert
Expert in ethical hacking, penetration testing, OWASP Top 10, vulnerability assessment, exploitation techniques, and security reporting. Use when the user mentions pentesting, ethical hacking, OWASP, vulnerability assessment, exploitation, or security testing, or when the task involves Penetration Testing…
kali-pentest
Execute authorized penetration testing via Kali Linux CLI tools over SSH or Docker. Covers: information gathering, vulnerability analysis, sniffing & spoofing, web/API testing, exploitation, password attacks, wireless, cloud-native security, RFID/NFC, VoIP/ICS, reverse engineering, forensics, post-exploitation/C2, and…