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-file-issue/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-file-issue)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-file-issue"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-file-issue.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.1 | $0.00034 | $0.02372 |
| Opus 5 | $0.00017 | $0.01186 |
| Sonnet 5 | $0.00007 | $0.00474 |
| Haiku 4.5 | $0.00003 | $0.00237 |
Grade A, and why
aget-file-issue 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 6d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-file-issue
File issues with private-first routing governance (L638). ALL issues go to {private-tracker}. Public issues on aget-framework/aget require explicit promotion.
Purpose
Structured issue filing with:
- Private-first routing: ALL agents →
{private-tracker}(L638) - Content sanitization at promotion boundary only
- Template selection (enhancement, bug, feature)
Input
/aget-file-issue <type> [title]
| Type | Description | Template |
|---|---|---|
enhancement |
Feature enhancement | ENHANCEMENT_REQUEST |
bug |
Bug report | BUG_REPORT |
feature |
New feature | FEATURE_REQUEST |
Execution
Step 1: Detect Agent Type
# Check for private fleet markers
if grep -q "gmelli\|private-" <<< "$PWD"; then
AGENT_TYPE="private"
elif grep -q '"fleet".*"private"' .aget/version.json 2>/dev/null; then
AGENT_TYPE="private"
elif git remote -v 2>/dev/null | grep -q "gmelli/"; then
AGENT_TYPE="private"
else
AGENT_TYPE="public"
fi
Step 2: Route to Private Tracker
ALL agents route to {private-tracker} (L638 private-first routing).
Agent type detection is retained for metadata tagging, but does NOT affect routing destination. Under the v2.0.0 policy, all agents — private fleet and public/remote — file to the private tracker.
Step 2.5: Resolve Routing Mode (v3.26 C-26-02 — #1845 fleet-universal supervisor relay)
Principal MC ruling (2026-07-05, enacted this cycle): no managed agent files issues directly — all filings relay through the managing supervisor. Supervisors are the filing authority (they file for themselves AND their managed agents).
Resolve the invoking seat + mode:
| Invoking seat | Resolved routing_mode | Step 4 behavior |
|---|---|---|
| Supervisor seat (archetype supervisor / manages agents) | direct |
file via gh issue create as below |
Managed agent (has a Managed By: supervisor) |
supervisor_intake (the flipped default) |
produce an INTAKE ARTIFACT, do NOT gh issue create |
| Managed agent, principal-supervised session (principal present and directing the filing) | direct permitted |
file directly; record routing_mode: direct (principal-supervised) in the body |
Explicit routing_mode: in the request |
as declared | honor it (lesson_first/supervisor_editorial per CAP-ISSUE-011..014) |
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.
- 6d ago First seen · 222 lines · 34 tokens per session scan A 490e1ee1dc91
aget-file-issue is a skill published in the GitHub repository aget-framework/aget (11 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 2,372 once invoked, about $0.0002 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-file-issue
File issues with L520 governance compliance.
aget-create-initiative
Scaffold approved initiative manifests at planning/initiatives/INIT-.md. Mirrors /aget-create-project STRICT (D71 Layer 2) — direct Write/Edit to planning/initiatives/ is PROHIBITED once this skill is invoked. Implements SOPinitiative.md (graduated procedure) + future AGETINITIATIVESPEC. Consumes PROPOSALinit.md…
aget-create-project
Create research projects with context-aware scaffolding. Reads AGET identity, searches prior work, pre-populates Due Diligence. Use when starting any formal AGET project.
aget-check-initiative
Read-only cross-system coherence check for initiatives. Aggregates state from KB, GitHub, Linear, and Slack, then reports alignment and drift.
aget-review-project
Mid-flight review of active project plans. Assesses gate progress, V-test completion, blockers, and recommendations. Use to evaluate project health.