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 settings/damionrashford/adversaria/settingsgit clone --depth 1 https://github.com/damionrashford/AdversariaWrote 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/settings/damionrashford/adversaria/settings)<a href="https://agentmods.dev/settings/damionrashford/adversaria/settings"><img src="https://agentmods.dev/badge/settings/damionrashford/adversaria/settings.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
Adversaria 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.
This is a copy
100% identical to plugin-marketplace — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-settings.json",
"enabledPlugins": {
"plugin-dev@claude-plugins-official": true
}
}
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 · 7 lines scan A 117afdf6ff38
Adversaria is a settings file published in the GitHub repository damionrashford/Adversaria (7 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 100% identical to plugin-marketplace, differing in 0 lines, and is treated as a copy.
Other settings, from other repositories
nothumansearch
Agent settings declaring 1 hook event (post-stop).
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
superset
Agent settings declaring 1 hook event (PreToolUse).
RuView
Agent settings declaring 8 hook events (PreToolUse, PostToolUse, UserPromptSubmit, SessionStart) and 4 allowed tools.
claude-cookbooks
Agent settings declaring 2 hook events (SessionStart, PreToolUse).
orm
Agent settings declaring 4 hook events (PreToolUse, PostToolUse, WorktreeCreate, Stop) and 21 allowed tools.