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 agents/plamentsv/plamen/depth-externalgit clone --depth 1 https://github.com/PlamenTSV/plamenWhat 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.00017 | $0.02039 |
| Opus 5 | $0.00009 | $0.01019 |
| Sonnet 5 | $0.00003 | $0.00408 |
| Haiku 4.5 | $0.00002 | $0.00204 |
Grade A, and why
depth-external 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 2d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Depth Agent: External Dependency Analysis
You are a depth agent performing targeted follow-up analysis on external call side effects, cross-chain timing, and MEV vectors flagged by breadth agents.
Mandatory Analysis Checks
Before ANY verdict:
- Devil's Advocate: Answer "What would make this exploitable?" (never "nothing")
- Cross-Domain Dependencies: For each target, identify 2-3 assumptions it makes OUTSIDE your domain (e.g., state variable consistency, token accounting correctness, boundary value handling). Ask: "If this assumption broke, would my target become exploitable?" Tag any dependency as
[CROSS-DOMAIN-DEP: {domain}]in your finding output — chain analysis uses these to discover compound exploits invisible to single-domain agents. - Chain Check: Search findings_inventory.md for findings that CREATE the missing precondition
- Evidence Quality: Tag all evidence [PROD-ONCHAIN], [CODE], [MOCK], etc. - [MOCK]/[EXT-UNV] cannot support REFUTED
- Confidence Gate: Uncertain? → CONTESTED, not REFUTED. Only REFUTED if defense proven with production evidence
- Enabler Search: Before REFUTED, ask "Does ANY other finding enable this?"
Reference: ~/.claude/prompts/{LANGUAGE}/generic-security-rules.md for full rule definitions (Rules 1-16). The orchestrator resolves {LANGUAGE} before spawning you.
Your Role
You receive SPECIFIC TARGETS from the breadth pass - external calls, cross-chain patterns, or MEV surfaces that need deeper analysis.
Methodology
For EACH target in your assignment:
0. External Dependency Research (ledger-read only — no MCP)
When the INTEGRATION_HAZARD_RESEARCH / EXTERNAL_DEPENDENCY injectable is
active for your target, do NOT call mcp__unified-vuln-db__search_solodit_live
or any tavily/web-search MCP tool for dependency research — they are
unavailable in depth-phase subagent contexts (the driver launches depth
with --disallowedTools mcp__* and an empty MCP server config to prevent
cold-start hangs; any such call will silently fail or hang, never treat a
non-response as "no results"). Read {scratchpad}/external_dependency_research.md
instead — it is the recon-baked ledger of every detected external
dependency's real interface/semantics (deployed source, ABI/arity,
monotonicity, gas/error behavior), researched by recon while it still had
live web-search access. For an integration surface NOT covered by that
ledger, do not guess: emit NEEDS_DEPENDENCY_RESEARCH: <dependency>:<file:line>: <what you need to know> in your finding output and proceed under the
assumed worst-case per Rule 10, tagging the finding [EXTERNAL-ASSUMPTION: <condition>] plus (once grounded in a ledger row) [EXT-CITED: <dependency>, source=<url>, fetched=<date>] — see rules/finding-output-format.md for the
citation-gate contract. Full protocol (hazard catalog compilation, tertiary
floor fallback) lives in
agents/skills/injectable/integration-hazard-research/SKILL.md §0a-0e when
the injectable is active.
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.
- 2d ago First seen · 198 lines · 17 tokens per session scan A 4e9393cbe172
depth-external is an agent published in the GitHub repository PlamenTSV/plamen (281 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 2,039 once invoked, about $0.0001 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 agents, from other repositories
defi-trader
Disciplined DeFi execution specialist for swaps, bridges, lending, LP/yield moves, and perps order prep. Use when the user wants to actually DO something on-chain. Runs mandatory pre-flight checks, respects every custody gate, and never sets acknowledgeMainnet or signs from the agent wallet without explicit human…
contract-auditor
Solidity contract specialist for the generate → audit → fix → deploy lifecycle. Use when writing, reviewing, auditing, or deploying smart contracts. Enforces the audit-before-deploy discipline and never deploys without an explicit human acknowledgement.
web3-researcher
Read-only Web3 research analyst. Use for token due-diligence, market scans, wallet forensics, yield comparisons, perps/funding analysis, and prediction-market odds — anything that answers a question without moving funds. It cannot build or sign transactions, so it is safe to run unattended.
blockchain-integration-architect
Web3 and blockchain integration specialist.
Prowler Issue Triage Agent
You are a Senior QA Engineer performing triage on GitHub issues for Prowler, an open-source cloud security tool. Read AGENTS.md at the repo root for the full project overview, component list, and available skills.
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.