Agent Skills Platform turns documented work and supporting evidence into tested, installable skills for coding agents. Teams use it to review, publish, maintain, and safely reuse agent workflows, with the catalogue entries serving as skills and plugins built for that ecosystem.
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 FrancyJGLisboa/agent-skill-creator --skill github-release-briefing-skillgit clone --depth 1 https://github.com/FrancyJGLisboa/agent-skill-creatorWrote 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/francyjglisboa/agent-skill-creator/github-release-briefing-skill)<a href="https://agentmods.dev/skills/francyjglisboa/agent-skill-creator/github-release-briefing-skill"><img src="https://agentmods.dev/badge/skills/francyjglisboa/agent-skill-creator/github-release-briefing-skill/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/francyjglisboa/agent-skill-creator/github-release-briefing-skill"><img src="https://agentmods.dev/badge/skills/francyjglisboa/agent-skill-creator/github-release-briefing-skill.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.00045 | $0.00460 |
| Opus 5.5 | $0.00018 | $0.00184 |
| Sonnet 5.5 | $0.00009 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
github-release-briefing-skill 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.
What it actually says
/github-release-briefing-skill
Create a current briefing for the latest published release of one public GitHub
repository. Run scripts/run_pipeline.py with an OWNER/REPOSITORY input.
The command uses GitHub's public REST endpoint, writes a Markdown briefing, and
does not authenticate, publish, modify a repository, or download release assets.
python3 scripts/run_pipeline.py --repository openai/openai-python --output release.md
Required behavior
- Reject malformed repository identifiers before any request.
- Retrieve only the latest published release and identify its tag, title, date, and URL.
- State clearly when a repository has no published release or is unavailable.
- Include the GitHub API source URL so a human can inspect the result.
Gotchas
- A GitHub "latest" release excludes drafts and prereleases according to the API's rules.
- This is dependency-awareness evidence, not a change-approval recommendation.
- Public API availability and release content can change after retrieval.
References
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- AGENTS.md 245 B
- discovery.json 2.5 KB
- evals/github-release-briefing.eval.md 192 B
- evals/golden/anthropic-sdk-python/input.txt 32 B
- evals/golden/openai-python/input.txt 21 B
- evals/golden/vercel-ai/input.txt 10 B
- README.md 223 B
- scripts/run_evals.py 2.1 KB runs code
- scripts/run_pipeline.py 2.3 KB runs code
- VERIFICATION.md 841 B
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 · 57 lines · 45 tokens per session scan A f48df6441f0b
github-release-briefing-skill is a skill published in the GitHub repository FrancyJGLisboa/agent-skill-creator (2,407 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 460 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-08-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
release-tag
Cut a release tag behind a real tier gate and cloud approval readback. The approval, task, approved commit, and resulting tag are bound; self-approval and HEAD drift fail closed. Prod prefixes remain refused.
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.