Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/aget-framework/template-advisor-agetnpx agentmods add skills/aget-framework/template-advisor-aget/aget-close-projectWrote 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-close-project)<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-close-project"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-close-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-close-project"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-close-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.00078 | $0.07280 |
| Opus 5.5 | $0.00031 | $0.02912 |
| Sonnet 5.5 | $0.00016 | $0.01456 |
| Haiku 4.5 | $0.00008 | $0.00728 |
Grade A, and why
aget-close-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 15d 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.
How it starts
The opening of the file, as written. The whole thing — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-close-project
Terminally close a PROJECT_PLAN with verifiable assertion, closure checklist, and deferred-surface handoff. Strict counterpart to /aget-create-project.
Input
$ARGUMENTS — PROJECT_PLAN filename (or slug; resolved against planning/) plus required
--disposition <Complete|Closed|CLOSED-PARTIAL|Abandoned|Superseded>
Mode Detection
| Input Pattern | Mode | Behavior |
|---|---|---|
| Empty | Interactive | List candidate plans (status=IN PROGRESS or all gates [x]), prompt for selection |
<filename> --disposition Complete |
Explicit | Resolve the plan and attempt a complete close |
<filename> --disposition <Closed|CLOSED-PARTIAL|Abandoned|Superseded> --reason <text> |
Explicit with reason | Required for every reasoned disposition; the reason explains but never selects the disposition |
<filename> --override <text> |
L178 override | Bypasses the ENTRY gate (Step 2) with recorded reason. Scoped deliberately: it does NOT bypass either arm of the Step 4.5 EXIT gate (4.5a completeness, 4.5b accounting). Before the gh#2250 reorder this flag was the routine way to close an honest plan — every closer-authored checklist row tripped Step 2 — which converted an exception route into the only route. It is exceptional again; a close needing it for closure-row reasons is now a defect report |
Project Closure Process
Step 0: Scope-Fit + Identity Check
- Read
.aget/identity.json— extractname,domain - Resolve PROJECT_PLAN path; verify file exists under
planning/ - If file absent: ERROR with candidate-list suggestion
Step 1: Input Analysis
Parse $ARGUMENTS:
- Plan filename or slug
- Required
--disposition <Complete|Closed|CLOSED-PARTIAL|Abandoned|Superseded>; no default - Optional
--reason <text>(required for Closed/Closed (Partial)/Abandoned/Superseded); reason text explains the explicit selection and SHALL NOT infer or select it - Optional
--override <text>(L178 path — bypasses the Step 2 ENTRY gate with recorded reason; does NOT bypass Step 4.5a or 4.5b)
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.
- 15d ago Changed 581581929454
- 1mo ago Changed · +173 lines 8ee20d6e7a52
- 1mo ago First seen · 263 lines · 78 tokens per session scan A 7a93f8a5a8dc
aget-close-project is a skill published in the GitHub repository aget-framework/template-advisor-aget (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 78 tokens to every session and 7,280 once invoked, about $0.0003 per session on Opus 5.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
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
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.
heaven-style
Use when coding, designing, reviewing, or writing documentation in TypeScript or Python projects.
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-campaign
Plan and track cross-project multi-repo campaigns — YAML overlays, repo rollups, objective fan-out, and MR status. Use for umbrella-scale coordinated work.