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 andregusman-raiz/a-gusman-claude --skill ag-registrar-issuegit clone --depth 1 https://github.com/andregusman-raiz/a-gusman-claudeWrote 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/andregusman-raiz/a-gusman-claude/ag-registrar-issue)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-registrar-issue"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-registrar-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/andregusman-raiz/a-gusman-claude/ag-registrar-issue"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-registrar-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00049 | $0.01335 |
| Opus 5.5 | $0.00020 | $0.00534 |
| Sonnet 5.5 | $0.00010 | $0.00267 |
| Haiku 4.5 | $0.00005 | $0.00134 |
Grade A, and why
ag-registrar-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 1mo 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ag-registrar-issue — Registrar Issue
Agent centralizado para criacao de GitHub Issues quando um problema nao pode ser resolvido imediatamente.
Outros agents enviam findings via SendMessage — este agent cria a issue no GitHub com contexto estruturado.
Invocation
Use the Agent tool with:
subagent_type:ag-registrar-issuename:issue-registrarmode:autorun_in_background:trueprompt: Compose from template below + $ARGUMENTS
Prompt Template
Repo: [owner/repo — detectar via git remote se nao fornecido]
Projeto path: [CWD or user-provided path]
Origem: [agent ID que encontrou o problema, ex: ag-depurar-erro]
Severidade: [P0-critical | P1-high | P2-medium | P3-low]
Titulo: [titulo conciso do problema]
Contexto: [descricao completa: o que foi tentado, por que nao foi resolvido, evidencias]
Arquivos: [arquivos relevantes, se conhecidos]
Labels: [bug, security, tech-debt, test-failure, performance, incident — auto-detect from context]
Workflow
1. Detectar Repo
# Se repo nao fornecido, detectar do git remote
cd [projeto_path]
gh repo view --json nameWithOwner -q '.nameWithOwner'
2. Dedup Check
Antes de criar, verificar se issue similar ja existe:
gh issue list --repo [repo] --state open --search "[keywords do titulo]" --json number,title,labels --limit 5
- Se encontrar issue com titulo >= 80% similar → adicionar COMENTARIO na issue existente em vez de criar nova
- Se nao encontrar → criar nova issue
3. Criar Issue
gh issue create --repo [repo] \
--title "[label-prefix] titulo" \
--label "[labels]" \
--body "$(cat <<'EOF'
## Contexto
[descricao do problema]
## Origem
Detectado por: `[agent ID]` durante execucao automatizada.
## Evidencias
- Arquivos: [lista de arquivos]
- Erro: [mensagem de erro ou descricao]
- Tentativas: [o que foi tentado e por que nao resolveu]
## Severidade
**[P0-P3]** — [justificativa]
## Sugestao de Resolucao
[se o agent origem forneceu sugestao]
---
*Issue criada automaticamente por ag-registrar-issue*
EOF
)"
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.
- 1mo ago First seen · 147 lines · 49 tokens per session scan A 267e03b8c8ba
ag-registrar-issue is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (18 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,335 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…