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 skills add aget-framework/template-advisor-aget --skill aget-review-projectgit clone --depth 1 https://github.com/aget-framework/template-advisor-agetWrote 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/aget-framework/template-advisor-aget/aget-review-project)<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-review-project"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-review-project/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/skills/aget-framework/template-advisor-aget/aget-review-project"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-review-project.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.00032 | $0.00872 |
| Opus 5 | $0.00016 | $0.00436 |
| Sonnet 5 | $0.00006 | $0.00174 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
aget-review-project 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 12d 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.
This is a copy
100% identical to aget-review-project — 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-review-project
Perform mid-flight review of an active project plan. Evaluates progress, identifies blockers, and generates recommendations.
Purpose
Enable AGETs to self-assess project health. Provides structured evaluation against success criteria and V-tests, supporting proactive course correction.
Input
$ARGUMENTS - Path to PROJECT_PLAN file (optional, defaults to current project context)
Execution
Step 1: Locate Project Plan
# If path provided
test -f "$ARGUMENTS" && echo "found"
# If no path, search for active projects
ls planning/PROJECT_PLAN_*.md 2>/dev/null
If multiple projects found, prompt user to select.
Step 2: Parse Project Structure
Extract from project plan:
- Metadata: Version, Status, Created, Author, POC
- Gates: All G-X sections with their V-tests
- Success Criteria: Target metrics
- Risk Assessment: Identified risks
Step 3: Evaluate V-Tests
For each gate, check V-test status:
Status indicators in plan:
- "✅" or "PASS" or "Complete" → Passed
- "❌" or "FAIL" → Failed
- "Pending" or unmarked → Not started
- "IN_PROGRESS" → Active
Calculate:
- Total V-tests
- Passed V-tests
- Completion percentage
Step 4: Identify Blockers
Scan for:
- Failed V-tests
- Dependencies on pending gates
- Risk items marked as materialized
- Items marked BLOCKED
Step 5: Generate Recommendations
Based on evaluation:
- Next Actions: Immediate steps for current gate
- Risk Alerts: Risks close to materializing
- Scope Adjustments: If behind schedule or blocked
Step 6: Output Report
Output Format
=== /aget-review-project ===
Project: <project name>
POC: <POC-XXX if applicable>
Status: <overall status>
Gate Progress:
G-0: [x] Complete (X/X V-tests)
G-1: [~] In Progress (X/Y V-tests)
G-2: [ ] Pending
...
G-F: [ ] Pending
Summary:
Total V-tests: <count>
Passed: <count> (<percentage>%)
Failed: <count>
Pending: <count>
Blockers:
[list or "None identified"]
Recommendations:
1. <specific action>
2. <specific action>
...
Overall Assessment:
<brief assessment of project health>
Health Status: [OK | WARN | CRITICAL]
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.
- 12d ago First seen · 151 lines · 32 tokens per session scan A b25a56abdcd9
aget-review-project is a skill published in the GitHub repository aget-framework/template-advisor-aget (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 32 tokens to every session and 872 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 aget-review-project, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
metagit-projects
Ongoing workspace and project management for OpenClaw and Hermes agents. Use when starting work, organizing repos, or before creating a new project folder so existing metagit projects are reused instead of duplicated.
metagit-rewrite-campaign
Orchestrate a reference-implementation rewrite across source and target repos using campaigns, parity registry conventions, objectives, and subagent handoffs.
metagit-control-center
Use when running metagit as an MCP control center for multi-repo awareness, guarded sync, and operational knowledge across ongoing agent tasks.
metagit-sharing-state
Configure shared coordination state (objectives, handoffs, approvals, events) across multiple agents and machines via METAGITSTATEURL, optional DynamoDB / MongoDB DocumentStore backends, and the ops HTTP path. Use when Hermes subagents, CI runners, or humans must see the same objective queue without Syncthing JSON…
daf-workflow
DevAIFlow session context loader — reads session metadata, issue tracker tickets, and context files. Auto-activates when DAFSESSIONNAME is set. Also useful when asked about current task, session status, or workflow steps for daf open, daf new, daf git new, daf jira new, and daf investigate.
metagit-aos
Compose ACL, task graph, scheduler, merge, and related coordination subsystems via metagit aos|coord status|doctor|next. Use when an operator or orchestrator needs one snapshot of coordination health or the next work envelope without launching models. Start with the day-1 quickstart for the canonical control loop.