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-assess-client/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-assess-client)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-assess-client"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-assess-client.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 95 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00013 | $0.00605 |
| Opus 5 | $0.00006 | $0.00302 |
| Sonnet 5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
aget-assess-client 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aget-assess-client
Assess client needs, constraints, and objectives to inform engagement scope. Produces structured needs assessment document.
Instructions
When this skill is invoked:
-
Gather Client Context
- Understand client's current state
- Identify stated goals and objectives
- Note organizational constraints
-
Identify Needs
- Explicit Needs: What client has stated
- Implicit Needs: What analysis reveals
- Distinguish needs from wants
-
Document Constraints
- Budget limitations
- Timeline requirements
- Technical constraints
- Organizational constraints
-
Prioritize
- Use impact/urgency matrix
- Identify quick wins vs. strategic initiatives
- Note dependencies between needs
-
Gap Analysis
- Current state assessment
- Desired state definition
- Gap identification
Output Format
## Client Needs Assessment
### Client Overview
| Attribute | Value |
|-----------|-------|
| Client | [Name/Context] |
| Assessment Date | [Date] |
| Scope | [Area of focus] |
### Identified Needs
#### Explicit Needs (Stated)
1. [Need 1]: [Description]
2. [Need 2]: [Description]
#### Implicit Needs (Discovered)
1. [Need 1]: [How discovered, why important]
### Constraints
| Type | Constraint | Impact |
|------|------------|--------|
| Budget | [Description] | [How it limits options] |
| Timeline | [Description] | [How it limits options] |
| Technical | [Description] | [How it limits options] |
### Priority Matrix
| Need | Impact | Urgency | Priority |
|------|--------|---------|----------|
| [Need 1] | High | High | P1 |
| [Need 2] | High | Low | P2 |
### Gap Analysis
| Area | Current State | Desired State | Gap |
|------|---------------|---------------|-----|
| [Area 1] | [Description] | [Description] | [What's missing] |
### Recommended Focus Areas
1. [Area]: [Why prioritize this]
Constraints
- C1: NEVER assume client needs without verification — assumptions lead to scope mismatch
- C2: NEVER ignore stated constraints — constraints bound the solution space
- C3: NEVER conflate wants with needs — distinguish to improve engagement focus
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.
- 8d ago First seen · 104 lines · 13 tokens per session scan A e1691b5d2fe4
aget-assess-client is a skill published in the GitHub repository aget-framework/aget (11 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 605 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.
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-file-issue
File issues with L520 governance compliance.
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-propose-actions
Propose ranked next-best actions with evidence grounding, time budgets, and execute-all default. Formalizes the fleet's highest-frequency interaction pattern.