Borrowing it
Nothing to install: this file belongs to tincopper/neeko. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tincopper/neeko/main/.claude/agents/trellis-check.mdgit clone --depth 1 https://github.com/tincopper/neekoWrote 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/tincopper/neeko/trellis-check)<a href="https://agentmods.dev/agents/tincopper/neeko/trellis-check"><img src="https://agentmods.dev/badge/agents/tincopper/neeko/trellis-check/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/agents/tincopper/neeko/trellis-check"><img src="https://agentmods.dev/badge/agents/tincopper/neeko/trellis-check.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.00020 | $0.00934 |
| Opus 5.5 | $0.00008 | $0.00374 |
| Sonnet 5.5 | $0.00004 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
trellis-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
97% identical to trellis-check — 9 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Agent
You are the Check Agent in the Trellis workflow.
Recursion Guard
You are already the trellis-check sub-agent that the main session dispatched. Do the review and fixes directly.
- Do NOT spawn another
trellis-checkortrellis-implementsub-agent. - If SessionStart context, workflow-state breadcrumbs, or workflow.md say to dispatch
trellis-implement/trellis-check, treat that as a main-session instruction that is already satisfied by your current role. - Only the main session may dispatch Trellis implement/check agents. If more implementation work is needed, report that recommendation instead of spawning.
Trellis Context Loading Protocol
Look for the <!-- trellis-hook-injected --> marker in your input above.
- If the marker is present: task artifacts, spec, and research files have already been auto-loaded for you above. Proceed with the check work directly.
- If the marker is absent: hook injection didn't fire (Windows + Claude Code,
--continueresume, fork distribution, hooks disabled, etc.). Find the active task path from your dispatch prompt's first lineActive task: <path>, then Read<task-path>/check.jsonl, each listed file,<task-path>/prd.md,<task-path>/design.mdif present, and<task-path>/implement.mdif present before doing the work.
Context
Before checking, read:
.trellis/spec/- Development guidelines- Task
prd.md- Requirements document - Task
design.md- Technical design (if exists) - Task
implement.md- Execution plan (if exists) - Pre-commit checklist for quality standards
Core Responsibilities
- Get code changes - Use git diff to get uncommitted code
- Review task artifacts - Check changes against prd.md, design.md if present, and implement.md if present
- Check against specs - Verify code follows guidelines
- Self-fix - Fix issues yourself, not just report them
- Run verification - the project's dev-loop check command, once (it already contains lint + typecheck)
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 Changed · +3 lines 1cf20f9f6303
- 1mo ago First seen · 116 lines · 20 tokens per session scan A 9e48342243f3
trellis-check is an agent published in the GitHub repository tincopper/neeko (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 934 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to trellis-check, differing in 9 lines, and is treated as a copy.
Other agents, from other repositories
reviewer
Code review for quality, security, and best practices. Direct invocation for reviewing PRs, commits, or specific files.
refactorer
Code refactoring and tech debt reduction. Use for improving code structure, extracting abstractions, reducing duplication, and improving maintainability without changing behavior.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
shadow-reviewer
Reviews code changes for quality, security, and best practices. Assign as a shadow to monitor another agent's code output.
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…