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-report-progressnpx skills add aget-framework/aget --skill aget-report-progressgit 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-report-progress)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-report-progress"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-report-progress.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.00009 | $0.00599 |
| Opus 5 | $0.00005 | $0.00300 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
aget-report-progress 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 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.
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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aget-report-progress
Report progress on current work including completion percentage, blockers, and remaining items. Supports handoff documentation.
Instructions
When this skill is invoked:
-
Assess Current State
- What's complete
- What's in progress
- What's remaining
-
Calculate Progress
- Completion percentage
- Velocity (if applicable)
- Estimated remaining
-
Identify Issues
- Current blockers
- Risks to completion
- Dependencies
-
Prepare Handoff (if needed)
- Context for continuation
- State of work
- Next steps
Output Format
## Progress Report
### Overview
| Field | Value |
|-------|-------|
| Work | [Task/Project Name] |
| Reporter | [Agent] |
| As Of | [Timestamp] |
| Status | [On Track/At Risk/Blocked] |
---
### Progress
**Completion**: [X]%
[███████████░░░░░░░░░] 55%
---
### Completed
1. [x] [Completed item 1]
2. [x] [Completed item 2]
3. [x] [Completed item 3]
---
### In Progress
1. [ ] [Current item]: [Status details]
---
### Remaining
1. [ ] [Remaining item 1]
2. [ ] [Remaining item 2]
---
### Blockers
| Blocker | Impact | Resolution Path |
|---------|--------|-----------------|
| [Blocker 1] | [Impact] | [How to resolve] |
---
### Risks
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| [Risk 1] | [H/M/L] | [H/M/L] | [Action] |
---
### Handoff (if session ending)
**Context**: [What needs to be known to continue]
**Current State**: [Where things stand]
**Next Steps**:
1. [What should happen next]
2. [Follow-up action]
**Files Modified**:
- [file1]: [What changed]
- [file2]: [What changed]
Constraints
- C1: NEVER overstate completion percentage — accurate progress essential for planning
- C2: NEVER hide blockers — blockers need attention
- C3: NEVER omit risks to protect optimistic view — honest risk reporting enables intervention
Related
- SKILL-039: aget-report-progress specification
- ONTOLOGY_worker.yaml: Progress, Task_Status, Handoff concepts
- CAP-WRK-002: Progress Reporting capability
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 · 127 lines · 9 tokens per session scan A 0fe4ad611a16
aget-report-progress is a skill published in the GitHub repository aget-framework/aget (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 9 tokens to every session and 599 once invoked, about $0.0000 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-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.