Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add dylan-buck/Clippos/plugin install clipposWrote 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/dylan-buck/clippos/clippos-config)<a href="https://agentmods.dev/commands/dylan-buck/clippos/clippos-config"><img src="https://agentmods.dev/badge/commands/dylan-buck/clippos/clippos-config.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.00027 | $0.00500 |
| Opus 5 | $0.00014 | $0.00250 |
| Sonnet 5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
clippos-config 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.
What it actually says
Invoke the clippos skill's configuration workflow with the user's arguments:
$ARGUMENTS
Resolve CLIPPOS_ROOT with the prologue documented in SKILL.md (env
var > HERMES_SKILL_DIR > CLAUDE_PLUGIN_ROOT > ~/.hermes/skills/clippos
~/.claude/skills/clippos>~/.codex/skills/clippos> newest plugin-cache checkout containingscripts/hermes_clippos.py>CLIPPOS_ROOTline in~/.config/clippos/.env>$PWD). Each candidate must containscripts/hermes_clippos.py. Runbash $CLIPPOS_ROOT/scripts/bootstrap-venv.sh; it is idempotent after a completed install and resumes incomplete.venvinstalls. Then resolveCLIPPOS_PYTHONto$CLIPPOS_ROOT/.venv/bin/pythonwhen executable, otherwisepython3.
Run "$CLIPPOS_PYTHON" "$CLIPPOS_ROOT/scripts/clippos_skill.py" config-check
first. The payload's top-level ready field reflects bins, render path, and
engine extras together — anything other than true means the run will fail
somewhere. If engine_imports.missing_required is non-empty, the active
interpreter lacks engine extras; tell the user to either install them in
that interpreter or point CLIPPOS_PYTHON at one that has them.
If the user provided defaults, write them with
"$CLIPPOS_PYTHON" "$CLIPPOS_ROOT/scripts/clippos_skill.py" config-write ....
For dev checkouts that lack a persisted root, also pass --root "$CLIPPOS_ROOT" once so the prologue resolves cleanly next time. If
required values are missing, ask only for the missing value needed next.
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 · 33 lines · 27 tokens per session scan A 8d3f9b7e8045
clippos-config is a command published in the GitHub repository dylan-buck/Clippos (9 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 500 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-31.
Other commands, from other repositories
vitaecontext-github
Audit or improve GitHub profile and repository SEO.
vitaecontext-vitaegraph
Create, validate, index, or use a private VitaeGraph.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
remember
Save text as a project memory in Rembric.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
review-video
Make a " Reviews" video — a fast, faceless VO montage of REAL, verified competitor reviews that names the recurring complaints and positions YOUR business as the alternative, then hands off to your own customer testimonials.