aget: Skill for Claude Code

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

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

A procedure for writing an engagement proposal: a document that defines work for a client, what will be delivered, and the boundaries of the engagement.

In plain words
What is it for?
Use it to prepare client proposals with an executive summary, in-scope and out-of-scope work, phases, deliverables, timelines, assumptions, and acceptance criteria.
Why use it?
It helps turn an unclear request into agreed scope, approach, deliverables, assumptions, dependencies, risks, and acceptance criteria. This reduces confusion about what is included and what is not.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

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-engagement/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-engagement

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/aget-framework/aget/aget-propose-engagement"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-propose-engagement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 642 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.00014 $0.00642
Opus 5 $0.00007 $0.00321
Sonnet 5 $0.00003 $0.00128
Haiku 4.5 $0.00001 $0.00064

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

Security

Grade A, and why

aget-propose-engagement 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 10d 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.

.claude/skills/aget-propose-engagement/SKILL.md · 131 lines

How it starts

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

aget-propose-engagement

Create engagement proposals outlining scope, approach, and deliverables. Produces structured proposal document with clear boundaries.

Instructions

When this skill is invoked:

  1. Verify Prerequisites

    • Client needs assessment completed
    • Constraints understood
    • Objectives clear
  2. Define Scope

    • In-scope items (explicit)
    • Out-of-scope items (explicit)
    • Scope boundaries
  3. Design Approach

    • Methodology selection
    • Phase breakdown
    • Key activities per phase
  4. Specify Deliverables

    • Concrete deliverable list
    • Acceptance criteria per deliverable
    • Delivery timeline
  5. Document Assumptions

    • Client-side requirements
    • Dependencies
    • Risk factors

Output Format

# Engagement Proposal: [Title]

**Date**: [YYYY-MM-DD]
**Client**: [Client Name]
**Prepared By**: [Agent Name]

---

## Executive Summary

[2-3 sentences describing the engagement value proposition]

---

## Scope

### In Scope
- [Item 1]: [Description]
- [Item 2]: [Description]

### Out of Scope
- [Item 1]: [Why excluded]
- [Item 2]: [Why excluded]

---

## Approach

### Methodology
[Description of approach/methodology]

### Phases

| Phase | Activities | Duration |
|-------|------------|----------|
| 1. [Name] | [Key activities] | [Timeframe] |
| 2. [Name] | [Key activities] | [Timeframe] |

---

## Deliverables

| Deliverable | Description | Acceptance Criteria |
|-------------|-------------|---------------------|
| [D1] | [What it is] | [How to verify complete] |
| [D2] | [What it is] | [How to verify complete] |

---

## Assumptions & Dependencies

### Assumptions
1. [Assumption 1]
2. [Assumption 2]

### Dependencies
- [Dependency 1]: [What we need from client]

---

## Success Criteria

1. [Measurable criterion 1]
2. [Measurable criterion 2]

---

## Next Steps

1. [Action 1]
2. [Action 2]

Constraints

  • C1: NEVER propose without prior needs assessment — proposals must be grounded in client needs
  • C2: NEVER leave scope ambiguous — clear scope prevents scope creep
  • C3: NEVER define deliverables without acceptance criteria — criteria enable completion verification

Read the full file on GitHub · 131 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. 10d ago First seen · 131 lines · 14 tokens per session scan A 77c3c38db286

Subscribe to this mod's changes

aget-propose-engagement is a skill published in the GitHub repository aget-framework/aget (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 642 once invoked, about $0.0001 per session on Opus 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.