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/aget-framework/aget/aget-create-skillnpx skills add aget-framework/aget --skill aget-create-skillgit 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-skill)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-create-skill"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-create-skill.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 | $0.00037 | $0.01188 |
| Opus 5 | $0.00018 | $0.00594 |
| Sonnet 5 | $0.00007 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade B, and why
aget-create-skill scanned grade B with 1 finding 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 4d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls .claude/skills/ | grep -q "<name>" Copies of this mod
1 near-identical copy found in the catalogue:
- aget-create-skill — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-create-skill
Create a new AGET skill following the standard development process per SOP_SKILL_DEVELOPMENT.md.
Input
$ARGUMENTS
Mode Detection
| Input Pattern | Mode | Behavior |
|---|---|---|
| Empty or blank | Interactive | Prompt for skill name |
<skill-name> |
Explicit | Create skill with provided name |
Skill Creation Process
Step 1: Name Validation
Validate the skill name follows S-V-O convention:
| Pattern | Valid | Examples |
|---|---|---|
/aget-<verb>-<object> |
✓ Default | /aget-create-skill, /aget-check-health |
/aget-<verb> |
✓ Intransitive | /aget-learn, /aget-checkpoint (grammar examples only; /aget-checkpoint was renamed to /aget-save-state, /aget-learn was never built) |
/aget-<phrasal-verb> |
✓ Exception | /aget-wake-up, /aget-wind-down |
| Other patterns | ✗ Invalid | /aget-skill-create (O-V not S-V-O) |
Check for existing skill:
ls .claude/skills/ | grep -q "<name>"
If skill exists, STOP and report conflict.
Step 2: Determine Skill Number
Check specs/skills/INDEX.md for next available SKILL-XXX number.
Current registry:
- SKILL-001 through SKILL-005: Existing
- SKILL-006: Reserved for /aget-create-project
- SKILL-007: This skill (/aget-create-skill)
- SKILL-008+: Available
Step 3: Create Skill Specification
Create specs/skills/SKILL-XXX_<name>.md with:
- Purpose section
- Requirements (R-SKILL-XXX-001, etc.) in EARS format
- Test cases
- Traceability section
Step 4: Create SKILL.md
- Create directory:
.claude/skills/<name>/ - Copy structure from
templates/skill/SKILL.template.md - Fill in required fields:
Required frontmatter:
---
name: <name>
description: <one-line description>
---
For skills with side effects (file writes, git operations):
disable-model-invocation: true
Instruction format (per L561 - Instruction Asymmetry):
- Use PROHIBITIVE form: "NEVER", "SHALL NOT", "DO NOT"
- Avoid affirmative form (~0% compliance)
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.
- 4d ago First seen · 149 lines · 37 tokens per session scan B 331f43c61b66
aget-create-skill is a skill published in the GitHub repository aget-framework/aget (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,188 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). 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 + deep bug finding.
aget-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818). Coverage and consistency mode.
aget-release-build
Execute gate deliverables with the Builder perspective of the Release Delivery Triad (L818). Speed-optimized execution mode.
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.