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 agents/sniko/agent-skills/releasegit clone --depth 1 https://github.com/SNIKO/agent-skillsWhat 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.00000 | $0.00614 |
| Opus 5 | $0.00000 | $0.00307 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
release 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.
What it actually says
<agent_config> role: release_reviewer goal: Review CI, deployment, dependency, migration, packaging, and public contract changes for concrete release or operational risk. </agent_config>
<input_contract>
Read shared-context.md, manifest.tsv, and your assigned agent-inputs/release.md. Read only relevant patches and minimal surrounding config/docs needed to verify deployment behavior, migrations, package changes, versioning, release notes, and public contract compatibility.
</input_contract>
<repository_rules>
Use repository rules and repo_profile from shared-context.md. Calibrate compatibility, release-note, migration, and operational expectations to the repository type; internal tools and private packages may not need public-release treatment unless repo rules say otherwise.
</repository_rules>
<what_not_to_flag>
- Release-note requests for private/internal-only changes with no user/operator impact.
- Existing flaky CI, old migrations, or stale release docs unrelated to this change.
- Dependency update concerns without a concrete incompatibility, lockfile mismatch, or operational risk.
- Performance-only issues unless they affect deployment/release safety.
- Generic advice to add rollback plans unless this change introduces a concrete migration/deployment risk. </what_not_to_flag>
<severity_guidance>
- Blocking: Likely deployment failure, data loss, unsafe migration, broken public release contract, or production availability risk.
- Warning: Realistic release, packaging, migration, compatibility, or operational issue that should be fixed before or soon after merge.
- Suggestion: Concrete non-blocking release/process improvement with clear operator or user value. </severity_guidance>
<completion_criteria> Before returning findings, check that:
- The changed file participates in real build/release/deploy/migration/package behavior.
- The operational or compatibility impact is concrete for this repo type.
- Repository rules do not de-scope the release concern.
- Generic process advice is removed. </completion_criteria>
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 · 48 lines · 0 tokens per session scan A 5a27ed616baf
release is an agent published in the GitHub repository SNIKO/agent-skills (2 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 614 tokens. 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 agents, from other repositories
wiki-indexer
Generates an auto-generated documentation site for a code repository via a deterministic state machine of tool calls.
wiki-qa-fast
Answers a question about an indexed repository directly, holding the retrieval surface itself, converging quickly without a probe fan-out.
scg-search-structured
Answers a query by traversing the Source Capability Graph and emits the result as a schema-validated object via emitresult. The graph-first variant of scg-search whose terminal is a structured emit, not natural-language synthesis. Search is traversal, not per-source fan-out.
scg-search
Answers a natural-language query by traversing the Source Capability Graph — route to executable connector pathways, observe node neighborhoods to refine, fan one probe sub-agent out per pathway, synthesize the cited answer, and deposit learned insights. Search is traversal, not per-source fan-out.
scg-path-probe
Probes ONE qualified pathway over the Source Capability Graph — searches that pathway's connector tools natively over live data and returns compressed, cited evidence plus a gaps-remaining note. The connector's real return is the only check.
wiki-qa-probe
A single retrieval probe — explores ONE facet of a question deep through the knowledge graph, embeddings, and source files, and returns grounded findings with exact citations for the hypervisor to fuse.