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 skills add aget-framework/template-advisor-aget --skill aget-file-issuegit clone --depth 1 https://github.com/aget-framework/template-advisor-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/template-advisor-aget/aget-file-issue)<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-file-issue"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-file-issue/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-file-issue"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-file-issue.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.01217 |
| Opus 5.5 | $0.00005 | $0.00487 |
| Sonnet 5.5 | $0.00002 | $0.00243 |
| Haiku 4.5 | $0.00001 | $0.00122 |
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 15d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-file-issue
File issues to appropriate repositories with L520 governance compliance (routing + sanitization).
Purpose
Structured issue filing with:
- Automatic destination routing based on agent type
- Content sanitization for public issues
- 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: Determine Destination
| Agent Type | Destination |
|---|---|
| Private Fleet | {private-tracker} |
| Public/Remote | aget-framework/aget |
Step 3: Prepare Content
For private agents filing to public repo, sanitize:
| Pattern | Replacement |
|---|---|
private-*-aget |
[PRIVATE-AGENT] |
private-*-AGET |
[PRIVATE-AGENT] |
gmelli/* |
[INTERNAL-REPO] |
\d+ agents? in fleet |
[N agents] |
SESSION_\d{4}-\d{2}-\d{2} |
[SESSION] |
Step 4: Validate
Check required fields:
- Title present
- Type valid (enhancement, bug, feature)
- Body not empty (for bugs)
Step 5: File Issue
# Private fleet agent
gh issue create \
--repo {private-tracker} \
--title "$TITLE" \
--body "$BODY" \
--label "type:$TYPE"
# Public/remote agent (sanitized)
gh issue create \
--repo aget-framework/aget \
--title "$TITLE" \
--body "$SANITIZED_BODY" \
--label "type:$TYPE"
Step 6: Report
Output:
Issue filed: <URL>
Destination: <repo>
Type: <type>
Sanitization: <applied/not-needed>
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.
- 15d ago Changed 59e633125c0d
- 1mo ago First seen · 188 lines · 12 tokens per session scan A ea03532ac533
aget-file-issue is a skill published in the GitHub repository aget-framework/template-advisor-aget (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,217 once invoked, about $0.0000 per session on Opus 5.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-31.
Other skills, from other repositories
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
daf-workflow
DevAIFlow session context loader — reads session metadata, issue tracker tickets, and context files. Auto-activates when DAFSESSIONNAME is set. Also useful when asked about current task, session status, or workflow steps for daf open, daf new, daf git new, daf jira new, and daf investigate.
heaven-style
Use when coding, designing, reviewing, or writing documentation in TypeScript or Python projects.
metagit-projects
Ongoing workspace and project management for OpenClaw and Hermes agents. Use when starting work, organizing repos, or before creating a new project folder so existing metagit projects are reused instead of duplicated.
metagit-rewrite-campaign
Orchestrate a reference-implementation rewrite across source and target repos using campaigns, parity registry conventions, objectives, and subagent handoffs.
metagit-campaign
Plan and track cross-project multi-repo campaigns — YAML overlays, repo rollups, objective fan-out, and MR status. Use for umbrella-scale coordinated work.