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 skills/tasitech/tasi-harness/code-reviewnpx skills add TasiTech/tasi-harness --skill code-reviewgit clone --depth 1 https://github.com/TasiTech/tasi-harnessWrote 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/tasitech/tasi-harness/code-review)<a href="https://agentmods.dev/skills/tasitech/tasi-harness/code-review"><img src="https://agentmods.dev/badge/skills/tasitech/tasi-harness/code-review.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.00021 | $0.00141 |
| Opus 5 | $0.00010 | $0.00071 |
| Sonnet 5 | $0.00004 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
code-review 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.
What it actually says
Code Review
Use this skill when asked to review a local project, inspect source files, or summarize risks in a patch.
Workflow
- Use
file_listto understand the workspace structure. - Read the smallest relevant files with
file_read. - When terminal is enabled, run focused commands such as
git diff --stat,npm test, or language-specific checks. - Report correctness bugs first, then security, reliability, maintainability, and style.
- Include exact file paths and concise suggested fixes.
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 · 18 lines · 21 tokens per session scan A 475f2a115ee0
code-review is a skill published in the GitHub repository TasiTech/tasi-harness (11 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 141 once invoked, about $0.0001 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 skills, from other repositories
test-repo
Use this skill to test strategy changes against a fresh test repository. Invoke when the user asks to "test against a test repo", "validate the changes", or wants to verify session hooks, commits, and checkpoint creation work correctly.
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…
changelog
Generate or update the CHANGELOG.md for a new release version. Use when the user says "generate changelog", "update changelog", "write release notes", or asks to prepare a changelog for a version like "changelog for 0.5.3".
e2e
Orchestrate E2E test triage and fix implementation: runs triage-ci then implement sequentially. Accepts test names, --agent, artifact path, or CI run reference. For individual phases, use /e2e:triage-ci, /e2e:debug, or /e2e:implement. Use when the user says "triage e2e", "fix e2e failures", or wants the full…
developer_guide
Guidance for using Developer Studio tools to inspect, edit, test, and review code workspaces safely.
custom_tool_builder_guide
Guidance for creating reusable Custom Tools from repos or folders.