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 agents/ooloth/dotfiles/nextjs-agentgit clone --depth 1 https://github.com/ooloth/dotfilesWhat 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 | $0.00057 | $0.00465 |
| Opus 5 | $0.00028 | $0.00233 |
| Sonnet 5 | $0.00011 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
nextjs-agent 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 61 lines · 57 tokens per session scan A 22795b9d8a8e
nextjs-agent is an agent published in the GitHub repository ooloth/dotfiles (24 stars, last pushed 11d ago), with no licence file. It adds 57 tokens to every session and 465 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-08-30.
Other agents, from other repositories
debugger
Performs evidence-based root-cause analysis: quotes the actual error, reproduces it, bisects what changed, forms one testable hypothesis, fixes the cause (not the symptom), and confirms the failing case now passes. Use when something is broken, a test fails, a stack trace appears, or you need fast diagnosis of a…
technical-documentation-architect
Restructures multi-file documentation sets: organizes docs-site information architecture (getting-started / guides / reference / architecture / contributing), validates content against actual code, removes legacy material with migration notes, enforces no-em-dash prose, and decides what to auto-generate versus…
curator
Sweeps documentation, formatting, naming, and cross-project conventions for consistency: audits the current state, references the governing standard, and applies the same fix across every instance, returning a deviation table. Use when you need a consistency pass, documentation hygiene, no-em-dash cleanup…
strategist
Executes write-capable multi-repo sweeps and batch operations: enumerates every target, dry-runs on one, presents a diff for approval, then applies across the full set with progress tracking and coverage verification. High blast radius (edits and runs scoped git/gh across many repos), so it gates on approval and halts…
architect
Designs interface-first system architecture: decomposes modules, enumerates 2-3 approaches with tradeoff tables, recommends a path on Easy-to-Change grounds, and stages phased delivery plans with per-phase verification. Use when you need a design doc, module boundaries, an API contract, or a phased rollout plan before…
writer
Authors concise, outcome-focused technical documentation for a single file: structures frontmatter and sections, leads with the action, uses tables over prose, avoids em dashes, verifies claims against source, and treats examples and gotchas as mandatory. Use for writing or rewriting one README, skill file, or API doc…