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 ZaxbyHub/opencode-swarm --skill check-skill-provenance-stamps-before-archiving-knowledge-entriesgit clone --depth 1 https://github.com/ZaxbyHub/opencode-swarmWrote 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/zaxbyhub/opencode-swarm/check-skill-provenance-stamps-before-archiving-knowledge-entries)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/check-skill-provenance-stamps-before-archiving-knowledge-entries"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/check-skill-provenance-stamps-before-archiving-knowledge-entries/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/zaxbyhub/opencode-swarm/check-skill-provenance-stamps-before-archiving-knowledge-entries"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/check-skill-provenance-stamps-before-archiving-knowledge-entries.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.00377 |
| Opus 5 | $0.00013 | $0.00188 |
| Sonnet 5 | $0.00005 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
check-skill-provenance-stamps-before-archiving-knowledge-entries 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 12d 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
check skill provenance stamps before archiving knowledge entries
Trigger
- (no explicit trigger metadata; cluster derived from category/tags)
Required Procedure
- check skill provenance stamps before archiving knowledge entries
- verify .opencode/skills/generated/*/SKILL.md source_refs against entries being archived
Forbidden Shortcuts
- (none recorded)
Delegation Template
When delegating a task affected by this skill, include:
SKILLS: file:.opencode/skills/generated/check-skill-provenance-stamps-before-archiving-knowledge-entries/SKILL.md
Reviewer Checks
- grep generated skills for the entry UUID being archived
- confirm no active skill depends on entry before archive
Source Knowledge IDs
- f80f0942-3236-4b5d-9b98-a23578676f27 — Before archiving knowledge entries, verify they are not source entries for active generated skills — archiving source entries triggers stale markers that silently exclude skills from injection.
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.
- 12d ago First seen · 48 lines · 26 tokens per session scan A 60c78c754f9a
check-skill-provenance-stamps-before-archiving-knowledge-entries is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (467 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 377 once invoked, about $0.0001 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
armada-contract
Co-write an armada contract (REQUIREMENTS.md) one question at a time. Use when drafting or updating a feature contract before implementation.
armada-gate
Run an evidence-gate checklist for each success criterion in the current phase. Use when checking if a phase is complete before marking it passed.
selftune
Self-improving skills toolkit that watches real agent sessions, detects missed triggers, grades execution quality, and improves skill packages through evals, replay, baselines, review, and post-deploy watch. Use when verifying or publishing a skill, improving instructions or routing, checking skill health, grading…
armada-dispatch
Dispatch subagents in parallel with disjoint file scope. Use when facing 2+ independent tasks, multiple files, or parallel phases. Triggers on: parallelize, dispatch subagents, run in parallel.
armada-ledger
Pick the right ledger for a finding. Use when writing defects, adversarial findings, or security findings. Triggers on: ledger, defect, adversarial, security finding, DEF-001, ADV-001, SEC-001.
armada-ponytail
Minimal, pragmatic code discipline for Clipper and Galleon. Laziest working solution, no fluff, no YAGNI bloat.