Borrowing it
Nothing to install: this file belongs to aget-framework/aget. 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/aget-framework/aget/main/.claude/skills/aget-create-project/SKILL.mdgit clone --depth 1 https://github.com/aget-framework/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/aget/aget-create-project)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-create-project"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-create-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/aget/aget-create-project"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-create-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.04607 |
| Opus 5.5 | $0.00016 | $0.01843 |
| Sonnet 5.5 | $0.00008 | $0.00921 |
| Haiku 4.5 | $0.00004 | $0.00461 |
Grade A, and why
aget-create-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- aget-create-project — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-create-project
Create a new AGET project with research-informed scaffolding per prior internal authoring plan.
Input
$ARGUMENTS
Mode Detection
| Input Pattern | Mode | Behavior |
|---|---|---|
| Empty or blank | Interactive | Prompt for type and name |
<type> <name> |
Explicit | Create project of specified type |
<topic> only |
Inference | Infer type from topic and AGET domain |
| Input contains evidence statements (interview data, gap analysis, L-doc citations, cross-reference synthesis) | Evidence-rich | Abbreviated research phase — use provided evidence, skip redundant searches |
Evidence-Rich Mode
Detection: Input contains 2+ of: specific L-doc references (L###), quantitative data (percentages, counts, session numbers), named sources (supervisor interviews, audit results), or cross-reference synthesis ("both supervisors agree...").
Behavior: Research Phase (Step 3) still executes per C-CP-003, but in abbreviated form:
- Step 3.1 (identity): Runs — always needed for project context
- Step 3.2 (L-docs): Abbreviated — search only L-docs explicitly cited in input, don't broad-search by topic keywords
- Step 3.3 (sessions): Abbreviated — note current session only (evidence was gathered in-session)
- Step 3.4 (similar projects): Runs — conflict check always needed
- Step 3.5 (vocabulary): Runs — vocabulary grounding always needed
Rationale: When the user provides rich evidence context (e.g., from supervisor interviews or gap analysis conducted in the same session), broad keyword searches duplicate work already done. The abbreviated research phase respects C-CP-003 (research is NOT skipped) while avoiding redundancy.
Supported Project Types
| Type | Template | Output Location |
|---|---|---|
research |
templates/poc/RESEARCH_PROJECT_PLAN.template.md |
planning/PROJECT_PLAN_<NAME>.md |
poc |
templates/poc/PROPOSAL.template.md |
planning/poc-proposals/POC-XXX-<name>.md |
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 9d6ea706a720
- 1mo ago First seen · 446 lines · 39 tokens per session scan A 640ece3b0630
aget-create-project is a skill published in the GitHub repository aget-framework/aget (12 stars, last pushed 7d ago), licensed Apache-2.0. It adds 39 tokens to every session and 4,607 once invoked, about $0.0002 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-30.
Other skills, from other repositories
aget-close-project
Close a PROJECTPLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECTPLAN…
aget-release-critique
Adversarial review with the Critic perspective of the Release Delivery Triad (L818). Dual mandate — spec coverage audit plus deep bug finding, asking what breaks in the field and which assumptions are wrong. Superseded by /aget-check-release.
aget-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818) — coverage and consistency mode, asking whether a spec covers all behaviors and where gaps or contradictions remain. Superseded by /aget-check-release.
aget-release-build
Execute release gate deliverables with the Builder perspective of the Release Delivery Triad (L818) — speed-optimized execution asking whether the work is done, fast, and functional. Superseded by /aget-create-release.
aget-file-issue
File issues with L520 governance compliance.
aget-propose-actions
Propose ranked next-best actions with evidence grounding, time budgets, and execute-all default. Formalizes the fleet's highest-frequency interaction pattern.