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/armanfatemi/nulliusWrote 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/plugins/armanfatemi/nullius/plugin)<a href="https://agentmods.dev/plugins/armanfatemi/nullius/plugin"><img src="https://agentmods.dev/badge/plugins/armanfatemi/nullius/plugin/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/armanfatemi/nullius/plugin"><img src="https://agentmods.dev/badge/plugins/armanfatemi/nullius/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
nullius 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 1mo 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
{
"name": "nullius",
"description": "Evidence Anchors for agent-written design docs: load-bearing claims about existing code carry citations a deterministic checker re-verifies. Includes the authoring skill and a [false-premise] reviewer kit.",
"version": "0.1.0",
"author": {
"name": "Arman Fatemi",
"url": "https://github.com/armanfatemi"
},
"homepage": "https://github.com/armanfatemi/nullius",
"repository": "https://github.com/armanfatemi/nullius",
"license": "MIT",
"keywords": ["evidence", "grounding", "design-docs", "review", "agents"]
}
What it installs
The manifest is a name and a version. 2 skills, 3 commands, 7 hooks travel with it, and installing the plugin installs all of them — 244 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill evidence-anchors A 104 tokens
- Skill setup A 68 tokens
- Command comply A 33 tokens
- Command audit A 23 tokens
- Command ground A 16 tokens
- Hook PreToolUse A not measured
- Hook PostToolUse A not measured
- Hook Stop A not measured
- Hook UserPromptSubmit A not measured
- Hook SessionEnd A not measured
- Hook SubagentStop A not measured
- Hook SessionStart A not measured
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.
- 1mo ago First seen · 14 lines scan A ed3ef4c86d64
nullius is a plugin published in the GitHub repository armanfatemi/nullius (5 stars, last pushed 15d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
argot
A guardrail that flags code foreign to a repo's own patterns — learned from git history. Bundles the argot-setup, argot-refresh, argot-check, argot-review-pr, argot-setup-ci, argot-write-rule, and argot-suggest-rules skills, the argot MCP server, and an opt-in, non-blocking pre-write guardrail hook.
aigon
aigon. Aigon is a local, open-source, spec-first software-delivery orchestrator for coding agents. It takes a Git-backed feature spec through isolated implementation, cross-agent review, and merge—using the agents and subscriptions you already have.
quality
Code quality skills — refactoring, naming conventions, and project structure.
xonovex-core
Apply software design, testing, review, version control, credentials, and accessibility practices.
wisp-agentdiff
Per-agent diff review for Claude Code parallel subagent workflows. Each subagent worktree captured automatically, tabbed TUI to approve, revert, or merge each one independently.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.