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 skills add armanfatemi/nullius --skill setupgit 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/skills/armanfatemi/nullius/setup)<a href="https://agentmods.dev/skills/armanfatemi/nullius/setup"><img src="https://agentmods.dev/badge/skills/armanfatemi/nullius/setup/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/skills/armanfatemi/nullius/setup"><img src="https://agentmods.dev/badge/skills/armanfatemi/nullius/setup.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.01267 |
| Opus 5 | $0.00034 | $0.00633 |
| Sonnet 5 | $0.00014 | $0.00253 |
| Haiku 4.5 | $0.00007 | $0.00127 |
Grade A, and why
setup 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 5d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nullius setup — guided onboarding
You are walking a human through onboarding nullius in this repository,
conversationally. Every actual read and write goes through the nullius kit
CLI via the Bash tool — this skill's allowed-tools frontmatter does not
grant you Write or Edit, so you have no way to touch
.claude/settings.json or any other file directly, even if you wanted to.
That is deliberate: you propose and relay; the CLI is what decides and
writes. If at any point completing a step seems to require writing a file
yourself, stop and tell the human what step is blocked and why, rather than
finding another way to write it — the two commands at the very end of this
skill are the only thing that ever installs hooks, and they are commands you
hand to the human, never something you run for them.
Do not use init --interactive in this skill. It opens a terminal prompt
UI that assumes a human is typing directly into a TTY; run through a Bash
tool call, its stdin is not a TTY, and it will just fall back to defaults
silently. Everything below drives the same underlying flow through explicit
flags instead — the flag surface a human's TTY session also answers into,
just supplied directly.
1. See what's already there
Run:
npx -y @nullius-inverba/kit doctor
Read the report. If nullius has never been set up here, most checks will report absence rather than failure — that's expected, not an error. Tell the human in one or two sentences what state you found, then continue.
2. Confirm the profile
Run:
npx -y @nullius-inverba/kit init --root . --dry-run
This prints the detected profile (plans, prs, or specs) and every file
it would write, without writing anything. Tell the human which profile was
detected and why (the tool prints its reason), and ask if they want a
different one — if so, everything below takes --profile <name> the same
way.
3. Propose Oracle globs — never write from a guess
Run:
npx -y @nullius-inverba/kit init --root . --suggest-oracle
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.
- 5d ago First seen · 126 lines · 68 tokens per session scan A 00041f4ea300
setup is a skill published in the GitHub repository armanfatemi/nullius (5 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 1,267 once invoked, about $0.0003 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-09-06.
Other skills, from other repositories
argot-setup-ci
Wire argot into a repository's GitHub Actions as a non-blocking configured check on every pull request — a job summary plus code-scanning annotations. Use when the user wants argot "in CI", "on PRs", "as a GitHub Action", or asks to "set up argot CI". Distinct from argot-setup (local checking) and argot-review-pr…
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.
argot-setup
Set argot up for a repository end to end — audit its history, decide what should shape its voice, fit, verify the fit actually catches things, tune the rules its own history says are noisy, and wire the places it runs (pre-write hook, pre-commit, MCP, CI). One sitting, one decision at a time, each proposed with the…
argot-check
Score your working changes with argot — flag code foreign to this repo's own patterns (unfamiliar dependencies, APIs, constructs), functions the repo already has, code filed in the wrong place, imports that break the repo's layering, and tests weakened, disabled, or deleted alongside a production change — before…
argot-write-rule
Codify a repo convention argot's built-ins don't cover into a scripted custom rule — a .argot/rules/NAME/rule.toml manifest plus a sandboxed Rhai script that fires exactly like a built-in, gated on a green fixture suite before it ever sees a real diff. Use when the user asks to "write an argot rule for X", "codify…
argot-refresh
Refresh Argot's committed fit snapshot safely — first diagnose why maintenance is recommended, re-audit corpus scope and structural path changes, review stale mutes and policy entries with the user, then fit locally, verify, and prepare the reviewed .argot/ update. Use when argot status, argot check, MCP, or CI…