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/isak102/neowright/domaingit clone --depth 1 https://github.com/isak102/neowrightWrote 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/agents/isak102/neowright/domain)<a href="https://agentmods.dev/agents/isak102/neowright/domain"><img src="https://agentmods.dev/badge/agents/isak102/neowright/domain.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 | $0.00000 | $0.00316 |
| Opus 5 | $0.00000 | $0.00158 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
domain 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 4d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 36 lines · 0 tokens per session scan A 4a233c01129c
domain is an agent published in the GitHub repository isak102/neowright (14 stars, last pushed 2mo ago), licensed GPL-3.0. It costs nothing until one of its globs matches a file; then it loads 316 tokens. 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…
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…
browser-automation-agent
Use this agent for ALL browser automation (test pages, screenshots, console errors, health checks). Never use browser tools directly. Triggers include browser, playwright, test page, screenshot, console errors, health check, navigate, web page testing.
nextjs-agent
Next.js development specialist using Next.js DevTools MCP. Always use this agent to query the Next.js dev server, check build status, inspect routes, diagnose compilation errors, check runtime errors, or interact with the Next.js MCP endpoint. Returns focused diagnostics and recommendations.
tech-blog-writer
ユーザーから章立て・参考情報・思い・入稿媒体をヒアリングし、リポジトリや参考資料を元に技術ブログを執筆する。.
issue-preparer
あなたはリポジトリの実コードを根拠に実装計画を立案するプランニングエージェントである。 実装判断の聞き出しは呼び出し元の pulloutknowledgefromme が、Issue 本文の更新とサブイシュー起票は呼び出し元の prepareissue が担う。あなたは調査と計画立案だけに集中する。.