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-execute-tasknpx skills add aget-framework/aget --skill aget-execute-taskgit clone --depth 1 https://github.com/aget-framework/agetWhat 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.00010 | $0.00596 |
| Opus 5 | $0.00005 | $0.00298 |
| Sonnet 5 | $0.00002 | $0.00119 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
aget-execute-task 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 2d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aget-execute-task
Execute defined tasks with progress tracking and deliverable production. Follows task definition through to completion.
Instructions
When this skill is invoked:
-
Validate Task
- Task definition exists
- Required inputs available
- Prerequisites met
-
Plan Execution
- Break into steps
- Identify deliverables
- Note checkpoints
-
Execute Steps
- Sequential execution
- Track progress
- Handle blockers
-
Produce Deliverables
- Create specified outputs
- Verify quality
- Document location
-
Report Completion
- Summary of work
- Deliverables list
- Any issues
Output Format
## Task Execution: [Task Name]
### Task Info
| Field | Value |
|-------|-------|
| Task | [Name/ID] |
| Started | [Timestamp] |
| Status | [In Progress/Blocked/Complete] |
---
### Progress
| Step | Description | Status |
|------|-------------|--------|
| 1 | [Step 1] | [Done/In Progress/Pending] |
| 2 | [Step 2] | [Done/In Progress/Pending] |
| 3 | [Step 3] | [Done/In Progress/Pending] |
**Progress**: [N]/[Total] steps ([X]%)
---
### Current Activity
[What is being worked on right now]
---
### Deliverables
| Deliverable | Status | Location |
|-------------|--------|----------|
| [D1] | [Pending/Complete] | [Path] |
| [D2] | [Pending/Complete] | [Path] |
---
### Blockers (if any)
1. **[Blocker]**: [Description]
- Impact: [What's blocked]
- Needed: [What would unblock]
---
### Completion Summary (when done)
**Completed**: [Timestamp]
**Duration**: [Time]
**Deliverables Produced**:
1. [Deliverable 1]: [Location]
**Notes**: [Any relevant observations]
Constraints
- C1: NEVER skip steps without explicit approval — task integrity requires step completion
- C2: NEVER claim completion without deliverables — deliverables are proof of completion
- C3: NEVER continue past blockers silently — blockers require human decision
Related
- SKILL-038: aget-execute-task specification
- ONTOLOGY_worker.yaml: Task, Deliverable, Task_Status concepts
- CAP-WRK-001: Task Execution 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.
- 2d ago First seen · 118 lines · 10 tokens per session scan A 987891659fa2
aget-execute-task is a skill published in the GitHub repository aget-framework/aget (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 596 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-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-wind-down
End AGET session with state capture and sanity checks.