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/builtin-agent-skillnpx skills add samugit83/redamon --skill builtin-agent-skillgit 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/builtin-agent-skill)<a href="https://agentmods.dev/skills/samugit83/redamon/builtin-agent-skill"><img src="https://agentmods.dev/badge/skills/samugit83/redamon/builtin-agent-skill.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 | $0.00150 | $0.01276 |
| Opus 5 | $0.00075 | $0.00638 |
| Sonnet 5 | $0.00030 | $0.00255 |
| Haiku 4.5 | $0.00015 | $0.00128 |
Grade A, and why
builtin-agent-skill 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 4d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- Adding a first-class attack technique the agent classifies and follows a workflow for.
For a user-uploadable workflow, use add-community-skill
instead. For a tool the agent calls, use agentic-tool-integration.
For per-skill tunable defaults, use project-settings-cascade.
Critical Rules
- ALWAYS add the skill id to
KNOWN_ATTACK_PATHSin agentic/state.py. It is the Pydantic validator's allowlist; miss it and the classifier's output is rejected at runtime even though every other layer is wired. - NEVER skip layers 8 and 9 (the chat-drawer layers). They live in webapp and
produce no error when forgotten: the skill classifies and badges, but the
drawer tooltip and one-click example prompts are silently missing. Layer 8 =
BUILT_IN_SKILLSin attack-skills/available/route.ts; Layer 9 = aSESubGroupin suggestionData.ts. - NEVER let classification keywords overlap an existing skill. Every enabled built-in competes for the same user message; overlapping keywords (e.g. saying "SQL" in an SSRF section) make both skills mis-route. Disambiguate in the "Key distinction" line of the section in classification.py.
- ALWAYS gate the workflow on the required tool inside
_inject_builtin_skill_workflow()(agentic/prompts/init.py:509):and "<tool>" in allowed_tools. Without the guard the agent gets instructions for a toolTOOL_PHASE_MAPblocks in that phase. - NEVER assume existing projects inherit the new skill.
builtInis a strict has-key check; existing projects need a jsonb update toattackSkillConfig. - Pick the snake_case id once and use that exact literal in all 9 layers.
grep -rn "<skill_id>" webapp/src agenticmust show it everywhere before you rebuild (an existing id likecve_exploitspans ~38 files).
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.
- 4d ago First seen · 86 lines · 150 tokens per session scan A 5ff098f3da93
builtin-agent-skill is a skill published in the GitHub repository samugit83/redamon (2,380 stars, last pushed yesterday), licensed MIT. It adds 150 tokens to every session and 1,276 once invoked, about $0.0007 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.
research-orchestrator
Parallel research with 4 specialized agents (Official, Practical, Edge Cases, Future).
tdd-agent
Autonomous test-driven development agent that writes code to make tests pass.
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…