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 skills/darkcofy/sqlprism/managing-project-releasesnpx skills add darkcofy/sqlprism --skill managing-project-releasesgit clone --depth 1 https://github.com/darkcofy/sqlprismWrote 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/darkcofy/sqlprism/managing-project-releases)<a href="https://agentmods.dev/skills/darkcofy/sqlprism/managing-project-releases"><img src="https://agentmods.dev/badge/skills/darkcofy/sqlprism/managing-project-releases.svg" alt="Measured on agentmods" 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.00061 | $0.00600 |
| Opus 5 | $0.00030 | $0.00300 |
| Sonnet 5 | $0.00012 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
managing-project-releases 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 4d 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
Managing Project Releases
Context
- GitHub repo: darkcofy/sqlprism
- GitHub Project: SQLPrism (project number 1, owner darkcofy)
- Labels:
enhancement,bug,chore(no sizing labels) - Branch convention:
feat-<name>,fix-<name>,chore-<name>
Workflow
- Read the implementation plan for the release from
.claude/plans/ - Create a milestone named after the release version (e.g.,
v1.0.1) - Decompose into issues — one per logical unit of work
- Write each issue in BDD format — see BDD-TEMPLATE.md
- Add all issues to the GitHub Project board
- Update dependency references with actual issue numbers after creation
Issue Decomposition Guidelines
Break work into issues that are:
- Independent where possible — parallelizable steps get separate issues
- Ordered by dependency — identify what blocks what
- Testable — every issue has BDD scenarios that become test cases
- Single responsibility — one issue = one logical change
Group by layer, not by file. Example layers:
- Schema/migration changes
- Renderer/parser changes
- Core logic (indexer, engine)
- API/tool surface (MCP tools, CLI commands)
- Tests (can be a single issue or per-layer)
Creating Issues
gh issue create \
--milestone "<version>" \
--label "<type>" \
--title "<concise title>" \
--body "$(cat <<'EOF'
<BDD body — see BDD-TEMPLATE.md>
EOF
)"
After creating all issues, add them to the project:
gh project item-add 1 --owner darkcofy --url "<issue_url>"
Then update dependency cross-references to use actual issue numbers.
Creating Milestones
gh api repos/darkcofy/sqlprism/milestones \
-f title="<version>" \
-f description="<one-line summary>" \
-f state="open"
Label Selection
| Label | When to use |
|---|---|
enhancement |
New features, new capabilities |
bug |
Fixing broken behavior |
chore |
Migrations, CI, deps, refactors |
What ships with it
1 file 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.
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.
- 4d ago First seen · 75 lines · 61 tokens per session scan A fd3fc5fcb4ea
managing-project-releases is a skill published in the GitHub repository darkcofy/sqlprism (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 600 once invoked, about $0.0003 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-09-01.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…