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.
git clone --depth 1 https://github.com/PlamenTSV/plamenWrote 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/commands/plamentsv/plamen/plamen-l1)<a href="https://agentmods.dev/commands/plamentsv/plamen/plamen-l1"><img src="https://agentmods.dev/badge/commands/plamentsv/plamen/plamen-l1.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.00000 | $0.00178 |
| Opus 5 | $0.00000 | $0.00089 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
plamen-l1 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.
What it actually says
plamen-l1
Arguments: $ARGUMENTS
Follow ~/.codex/skills/plamen/SKILL.md with the L1 wizard reference. New configs must set pipeline = l1 and cli_backend = codex.
Do not manually orchestrate Plamen phases and do not spawn audit agents yourself. Launch only the shared Python driver:
python C:\\Users\\plmnt\\.codex\\plamen\\scripts\\plamen_driver.py "{CONFIG_PATH}"
Fresh restart:
python C:\\Users\\plmnt\\.codex\\plamen\\scripts\\plamen_driver.py --fresh "{CONFIG_PATH}"
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 · 24 lines · 0 tokens per session scan A c50a5ec874b4
plamen-l1 is a command published in the GitHub repository PlamenTSV/plamen (286 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 178 tokens. 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-09-03.
Other commands, from other repositories
krait
Run a complete multi-phase security audit on the target codebase.
krait-poc
Write and run a valid Foundry proof-of-concept that proves (or disproves) a Solidity exploit by asserting the actual harm on a forked chain or against local source.
dashboard
Open the ChainGPT marketplace dashboard (localhost web UI — Overview, Skills, Activity, Health, About).
krait-review
Re-examine findings killed by the Critic's automatic gates. Catches over-filtering without compromising the main report's zero-FP standard.
krait-quick
Run a streamlined audit: Recon → Detection → Verification → Report. Skips state inconsistency analysis and cross-feed iteration for speed.
pre-deploy
Interactive pre-launch security checklist — walk the operational and code-safety gates and produce a final GO / NO-GO with each item PASS / FAIL / N-A.