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-promote-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-promote-issue)<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-promote-issue"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-promote-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-promote-issue"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-promote-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.00000 | $0.01092 |
| Opus 5 | $0.00000 | $0.00546 |
| Sonnet 5 | $0.00000 | $0.00218 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
aget-promote-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 10d 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.
This is a copy
91% identical to aget-promote-issue — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-promote-issue
Promote issues from the private tracker (gmelli/aget-aget) to the public tracker (aget-framework/aget) through governed content sanitization and principal approval. Prevents private information leakage at the promotion boundary.
Purpose
The private-first routing model (L638) means all issues start in gmelli/aget-aget. Some need public visibility. This skill governs that boundary crossing with content sanitization (R-ISSUE-011), principal approval, and source traceability.
Input
issue_number - The private issue number to promote (required)
Examples:
/aget-promote-issue #834— Promote issue 834/aget-promote-issue #834 --dry-run— Preview sanitized content without filing
Execution
Step 1: Read Source Issue
gh issue view {issue_number} --repo gmelli/aget-aget --json title,body,labels,state
Verify: issue exists, is open, belongs to gmelli/aget-aget.
Step 2: Content Sanitization
Scan title and body for private patterns:
| Pattern | Example | Action |
|---|---|---|
| Private agent names | private-*-aget, private-*-AGET |
BLOCK |
| Private repo refs | gmelli/* |
BLOCK |
| Fleet size | "32 agents", "40 agents" | BLOCK |
| Internal project IDs | FLEET-*-### |
BLOCK |
| Session references | SESSION_2026-* |
BLOCK |
If ANY pattern detected: display matches, ask user to revise source issue first.
Step 3: Draft Promoted Content
- Title: Sanitized version of source title
- Body: Sanitized body + footer:
_Promoted from internal tracker._ - Labels: Transfer
type:*anddomain:*labels. Do NOT transferowner:*orstatus:*.
Step 4: Principal Approval Gate
Display drafted content and checklist:
=== Promotion Preview: #{issue_number} ===
Title: {sanitized_title}
Body: {sanitized_body}
Labels: {transferred_labels}
Destination: aget-framework/aget
Checklist:
- [ ] Principal approval (R-ISSUE-011)
- [ ] Content sanitization passed (R-ISSUE-012)
- [ ] Source traceability included (R-ISSUE-013)
- [ ] Label mapping complete (R-ISSUE-014)
Proceed? [Y/N]
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.
- 10d ago First seen · 128 lines · 0 tokens per session scan A 7239f4467208
aget-promote-issue is a skill published in the GitHub repository aget-framework/template-advisor-aget (2 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,092 tokens. A static security scan graded it A with 0 findings. It is 91% identical to aget-promote-issue, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
clawrium-release-announcements
Daily — draft a release blog post, open a PR, iterate on comments until merged.
blog-author
Watch ric03uec/clawrium release tags; draft a short blog post per user-visible feature as a PR against blog/.
release-watcher
Watch upstream Claw releases and clawrium discussions; surface top 3 feature candidates to Devashish via Discord DM for approve/skip.
perseus
Use when you need a bounded, local Perseus context render before an assistant reads project state. Perseus resolves selected workspace inputs such as git, services, sessions, and task notes into markdown. Use for deterministic session starts, workspace audits, and explicit context handoffs.
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
release
Cut a new release by tagging a version and publishing via GitHub, which triggers the PyPI Trusted Publishing and docs-deploy workflows. Use when asked to "make a release", "cut a version", or "publish".