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-provide-feedback/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-provide-feedback)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-provide-feedback"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-provide-feedback.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.00579 |
| Opus 5 | $0.00005 | $0.00290 |
| Sonnet 5 | $0.00002 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
aget-provide-feedback 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aget-provide-feedback
Provide structured feedback with severity classification. Balances constructive criticism with positive observations.
Instructions
When this skill is invoked:
-
Review Work Product
- Understand context and goals
- Identify what was attempted
- Note constraints author faced
-
Classify Feedback
- Blocking: Must fix, prevents acceptance
- Suggestion: Should consider, improves quality
- Nitpick: Minor, stylistic
- Praise: Positive, worth acknowledging
-
Make Actionable
- Specific location
- Clear description
- Suggested resolution
-
Balance
- Include positive observations
- Constructive tone
- Proportionate to significance
Output Format
## Feedback: [Work Product]
### Summary
| Severity | Count |
|----------|-------|
| Blocking | [N] |
| Suggestion | [N] |
| Nitpick | [N] |
| Praise | [N] |
---
### Blocking Issues
1. **[Location]**
- Issue: [Description]
- Impact: [Why this blocks]
- Suggestion: [How to resolve]
---
### Suggestions
1. **[Location]**
- Observation: [What could be better]
- Rationale: [Why it matters]
- Suggestion: [Specific improvement]
---
### Nitpicks
1. **[Location]**: [Minor observation]
---
### Positive Observations
1. **[Location]**: [What was done well]
2. **General**: [Overall strength]
---
### Overall Assessment
[Brief summary of quality level and key points]
Severity Guidelines
| Severity | Criteria | Examples |
|---|---|---|
| Blocking | Prevents functionality, correctness, or compliance | Bug, security issue, spec violation |
| Suggestion | Improves quality, maintainability, clarity | Refactoring opportunity, better naming |
| Nitpick | Style, preference, minor | Formatting, comment wording |
| Praise | Notable positive | Elegant solution, thorough testing |
Constraints
- C1: NEVER classify all feedback as blocking — severity inflation reduces effectiveness
- C2: NEVER provide vague feedback — specific feedback enables action
- C3: NEVER use harsh or personal language — constructive tone maintains collaboration
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 · 111 lines · 11 tokens per session scan A ce84977c3d8c
aget-provide-feedback is a skill published in the GitHub repository aget-framework/aget (11 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 579 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-release-critique
Adversarial review with the Critic perspective of the Release Delivery Triad (L818). Dual-mandate: spec coverage audit + deep bug finding.
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-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.