aget: Skill for Claude Code

.claude/skills/aget-propose-skill/SKILL.md

aget-propose-skill is a skill for Claude Code from aget-framework/aget. It costs 33 tokens per session (864 once invoked), scanned A, original, Apache-2.0.

A review step for proposing new coding-agent skills before they are built. It collects the skill’s purpose, triggers, category, and scope, then checks its name and uniqueness.

In plain words
What is it for?
Use it when you have an idea for a new skill and want to prepare it for review and approval before implementation.
Why use it?
It helps prevent skills from being added without a clear purpose or review. It also catches naming, duplicate, and missing-trigger problems early.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths.

This is aget-framework/aget's own configuration. It tells Claude Code how to work on aget itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aget configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/aget-framework/aget/main/.claude/skills/aget-propose-skill/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/aget-framework/aget

Made for: Claude Code.

Wrote 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.

agentmods badge for aget-propose-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/aget-framework/aget/aget-propose-skill/github.svg)](https://agentmods.dev/skills/aget-framework/aget/aget-propose-skill)
Your own site
<a href="https://agentmods.dev/skills/aget-framework/aget/aget-propose-skill"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-propose-skill/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.

agentmods 80×15 button for aget-propose-skill

Your own site · 80×15
<a href="https://agentmods.dev/skills/aget-framework/aget/aget-propose-skill"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-propose-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 864 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00864
Opus 5.5 $0.00013 $0.00346
Sonnet 5.5 $0.00007 $0.00173
Haiku 4.5 $0.00003 $0.00086

Measured 15d ago against content hash c8d022c2b1cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

aget-propose-skill 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/aget-propose-skill/SKILL.md · 152 lines

How it starts

The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/aget-propose-skill

Create a structured skill proposal before implementation. Follows governance pattern: propose → review → approve → implement.

Purpose

Prevent unreviewed skill proliferation. Forces deliberate consideration of skill purpose, triggers, and design before investing in implementation.

Input

$ARGUMENTS - Skill name or idea description

Execution

Step 1: Gather Information

Collect from user:

  1. Skill name (must follow aget-{verb}-{object} pattern)
  2. Purpose - What problem does this skill solve?
  3. Triggers - What user actions/phrases should invoke it? (minimum 2)
  4. Category - Governance, Creation, Monitoring, Learning, Planning, Fleet Ops?
  5. Scope - Universal (all agents) or Agent-specific?

Step 2: Validate Constraints

C1: Name Format

Pattern: aget-{verb}-{object}
Valid:   aget-check-evolution, aget-record-lesson
Invalid: healthcheck-evolution, aget_record_lesson, myskill

C2: Uniqueness

# Check if skill already exists
test -d .claude/skills/$SKILL_NAME && echo "EXISTS" || echo "OK"

C3: Minimum Triggers

Triggers provided >= 2

If any constraint fails, report error and stop.

Step 3: Create Proposal

Create file at planning/skill-proposals/PROPOSAL_{name}.md:

# Skill Proposal: {name}

**Date**: {YYYY-MM-DD}
**Author**: {agent}
**Status**: PROPOSED

---

## Summary

**Name**: {name}
**Category**: {category}
**Scope**: {Universal/Agent-specific}

## Purpose

{What problem does this solve?}

## Triggers

When user says:
- "{trigger 1}"
- "{trigger 2}"
- ...

## Design Notes

{Initial design considerations}

## Dependencies

{Other skills or resources needed}

## Approval

- [ ] Principal reviewed
- [ ] Design approved
- [ ] Ready for implementation

---

*Use `/aget-create-skill {name}` to implement after approval.*

Step 4: Update Index (if exists)

If planning/skill-proposals/INDEX.md exists, add entry.

Step 5: Report

Proposal created: planning/skill-proposals/PROPOSAL_{name}.md

Next steps:
1. Review proposal with principal
2. Get approval
3. Run /aget-create-skill {name} to implement

Read the full file on GitHub · 152 lines

Changes

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.

  1. 15d ago Changed c8d022c2b1cd
  2. 1mo ago First seen · 152 lines · 33 tokens per session scan A 473a0d2e29fe

Subscribe to this mod's changes

aget-propose-skill is a skill published in the GitHub repository aget-framework/aget (12 stars, last pushed 7d ago), licensed Apache-2.0. It adds 33 tokens to every session and 864 once invoked, about $0.0001 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.

Related

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-framework/template-advisor-aget · 78 tokens

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-framework/template-advisor-aget · 57 tokens

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-framework/template-advisor-aget · 53 tokens

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-framework/template-advisor-aget · 49 tokens

aget-file-issue

File issues with L520 governance compliance.

aget-framework/template-advisor-aget · 12 tokens

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.

aget-framework/template-advisor-aget · 33 tokens