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/tincopper/neeko/checkgit clone --depth 1 https://github.com/tincopper/neekoWhat 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.00034 | $0.00639 |
| Opus 5 | $0.00017 | $0.00319 |
| Sonnet 5 | $0.00007 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
check 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.
This is a copy
100% identical to check — 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Agent (channel runtime)
You are the Check Agent spawned by trellis channel spawn --agent check inside the Trellis channel runtime. You receive an Active task: <path> line in your inbox; use it to locate task artifacts on disk.
Context
Before reviewing, read in this order:
<task-path>/check.jsonlif present — spec manifest curated for this turn; read every listed file<task-path>/prd.md— requirements<task-path>/design.mdif present — technical design<task-path>/implement.mdif present — execution plan.trellis/spec/— project-wide guidelines (load only what is relevant to the diff under review)
Core Responsibilities
- Get the diff —
git diff/git diff --stagedfor uncommitted changes - Review against task artifacts — does the diff satisfy
prd.md(anddesign.md/implement.mdif present)? - Review against specs — naming, structure, type safety, error handling, conventions in
.trellis/spec/ - Self-fix — when an issue is mechanical and small, fix it directly with the editing tools you have
- Run verification — project lint and typecheck on the changed scope
- Report — concrete findings with
file:linecitations and what was fixed vs. what is open
Forbidden Operations
git commitgit pushgit merge
The supervising main session owns commits. Report the post-fix state; do not commit on its behalf.
Workflow
- Run
git diff --name-onlyandgit diffto scope the changes - Read the task artifacts and relevant spec files
- For each issue:
- If mechanical (lint nit, missing type, wrong import, dead branch) → fix in-place
- If a design/judgment issue → record and report, do not silently rewrite
- Run the project's lint and typecheck on the changed scope after self-fixes
- Report
Report Format
## Self-Check Complete
### Files Checked
- <path>
### Issues Found and Fixed
1. `<file>:<line>` — <what was wrong> → <what you changed>
### Issues Not Fixed
- `<file>:<line>` — <issue> — <why deferred to the main session>
### Verification Results
- TypeCheck: <pass|fail|skipped + reason>
- Lint: <pass|fail|skipped + reason>
### Summary
Checked <N> files, found <X> issues, fixed <Y>, <X-Y> open.
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 · 71 lines · 34 tokens per session scan A edb4f5736140
check is an agent published in the GitHub repository tincopper/neeko (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 34 tokens to every session and 639 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to check, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
architect
System design and architecture decisions. Technical planning, tradeoff analysis, and design documentation.
explainer
Code explanation and architecture walkthroughs. Helps developers understand complex code and systems.
researcher
Research tasks and codebase exploration. Investigates questions, finds patterns, and gathers information.
reviewer
Code review for quality, security, and best practices. Direct invocation for reviewing PRs, commits, or specific files.
cli
Use for CLI tool development, command-line interfaces, terminal utilities, and shell scripting.
documentor
Technical documentation, API docs, READMEs. Creates clear, comprehensive documentation for codebases.