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-create-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-create-project)<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-create-project"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-create-project.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.1 | $0.00039 | $0.04637 |
| Opus 5 | $0.00019 | $0.02318 |
| Sonnet 5 | $0.00008 | $0.00927 |
| Haiku 4.5 | $0.00004 | $0.00464 |
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 7d 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-create-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 — 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 PROJECT_PLAN_AGET_CREATE_PROJECT_V2.md.
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.
- 7d 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/template-advisor-aget (2 stars, last pushed 7d ago), licensed Apache-2.0. It adds 39 tokens to every session and 4,637 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-create-project, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
follow-up-after-call
Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions…
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.