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/agenturehq/agenture-loop/code-reviewnpx skills add AgentureHQ/agenture-loop --skill code-reviewgit clone --depth 1 https://github.com/AgentureHQ/agenture-loopWhat 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.00056 | $0.01184 |
| Opus 5 | $0.00028 | $0.00592 |
| Sonnet 5 | $0.00011 | $0.00237 |
| Haiku 4.5 | $0.00006 | $0.00118 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Read-only review of the codebase. Produces actionable backlog tasks for findings. Does not modify code.
When to Use
Run periodically — after completing a batch of tasks, before a release, or when the codebase has accumulated drift from multiple contributors or agents working on isolated tasks.
Workflow
- Determine scope — ask the user what to review: the entire codebase, a specific module, or recent changes (e.g.,
git diff main..HEADor a date range). - Run the checklist — evaluate each category below. For each finding, note the file, line, and a concrete recommendation.
- Present summary to user — show findings grouped by category and severity. Discuss with user which findings warrant action.
- Create backlog tasks — for each approved finding (or group of related findings), create a task file in
tasks/backlog/following the task management standard. These tasks are then executed later via/agn:task-implement.
Review Checklist
1. Dead Code & Unused Artifacts
- Unused imports, variables, functions, classes, and modules
- Commented-out code blocks (belongs in version control, not in source)
- Unused dependencies in
requirements.txt,package.json, etc. - Orphaned configuration files or scripts that no longer serve a purpose
2. Type Safety
- Python: all function signatures should have type hints for parameters and return values.
- TypeScript: no
anytypes without justification. Prefer interfaces over inline types for reused shapes. - Data transfer boundaries (API endpoints, serialization) should have explicit type definitions.
3. Function & Module Design
- Functions should be small and do one thing. If a function exceeds ~30 lines, evaluate whether it can be decomposed.
- Modules should have clear single responsibility.
- Nesting depth: flag functions with more than 3 levels of nesting.
4. DRY Violations
- Duplicated logic across files or modules.
- Similar but slightly different implementations of the same concept.
- Opportunities to extract shared utilities, base classes, or mixins.
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 · 121 lines · 56 tokens per session scan A acede8ec4b79
code-review is a skill published in the GitHub repository AgentureHQ/agenture-loop (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,184 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-31.
Other skills, from other repositories
agentflow
Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution.
agent-spec-estimate
CRITICAL: Use for estimating work effort from agent-spec Task Contracts. Triggers on: estimate, estimation, how long, work effort, round count, time estimate, scope, sizing, cost, budget, planning, sprint, capacity, "how many rounds", "how long will this take", "estimate this spec", 估算, 工作量, 多久, 时间估算, 预估, 工时, 规模…
backlog-grooming
Review Agiflow Planning tasks for readiness, prioritize approved work, group related tasks into work units, and promote ready tasks to Todo. Use when grooming a backlog, organizing planned tasks, creating work units, or deciding what should be executed next.
project-plan
Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog.
refine-task
Refine an existing Agiflow task into an unambiguous, testable specification without expanding its intended outcome. Use when a task is vague, lacks acceptance criteria, has unclear scope or dependencies, or is not ready for backlog grooming.
triage
Diagnose stalled, blocked, overloaded, or unhealthy Agiflow projects and recommend specific corrective actions. Use for project health checks, blocked work, conflicting priorities, obsolete tasks, overloaded assignees, or an unmanageable backlog.