Borrowing it
Nothing to install: this file belongs to mcpc-tech/mcpc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mcpc-tech/mcpc/main/.agents/skills/release-v5-acp/SKILL.mdgit clone --depth 1 https://github.com/mcpc-tech/mcpcWrote 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/mcpc-tech/mcpc/release-v5-acp)<a href="https://agentmods.dev/skills/mcpc-tech/mcpc/release-v5-acp"><img src="https://agentmods.dev/badge/skills/mcpc-tech/mcpc/release-v5-acp/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/mcpc-tech/mcpc/release-v5-acp"><img src="https://agentmods.dev/badge/skills/mcpc-tech/mcpc/release-v5-acp.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.00043 | $0.00734 |
| Opus 5 | $0.00022 | $0.00367 |
| Sonnet 5 | $0.00009 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
release-v5-acp 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 9d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release ACP AI Provider for AI SDK v5
Release @mcpc/acp-ai-provider package for the AI SDK v5 compatibility line
(version 0.1.x).
Version Compatibility
| ACP Version | AI SDK Version | Branch |
|---|---|---|
0.2.x |
v6 | main |
0.1.x |
v5 | release-v5 |
When to Use
- Fix bugs in AI SDK v5 compatibility line
- Release new 0.1.x versions
- Backport fixes from main to release-v5
Steps
1. Switch to release-v5 Branch
git checkout release-v5
git pull origin release-v5
2. Apply Fixes (if needed)
Cherry-pick fixes from main:
git cherry-pick <commit-hash>
Or manually apply changes. Note: release-v5 uses AI SDK V2 types
(LanguageModelV2StreamPart), main uses V3 (LanguageModelV3StreamPart).
3. Update Version
Edit packages/acp-ai-provider/deno.json:
{
"version": "0.1.x" // Increment patch version
}
4. Verify Changes
deno fmt packages/acp-ai-provider/
deno check packages/acp-ai-provider/mod.ts
deno test --allow-all packages/acp-ai-provider/tests/
5. Commit
git add packages/acp-ai-provider/deno.json
git commit -m "chore(acp-ai-provider): bump version to 0.1.x"
6. Create and Push Tag
git tag v0.1.x # Use the new version
git push origin release-v5
git push origin v0.1.x
7. Update Downstream Packages (Optional)
If core or other packages need to use the new version:
-
Update
packages/core/deno.json:"@mcpc/acp-ai-provider": "npm:@mcpc-tech/acp-ai-provider@^0.1.x" -
Bump core version (0.3.x → 0.3.x+1)
-
Sync all dependent packages to use new core version
-
Tag core:
git tag v0.3.x+1
Key Differences from Main
| Aspect | release-v5 | main |
|---|---|---|
| AI SDK | V2 | V3 |
| Version | 0.1.x | 0.2.x |
| Types | LanguageModelV2StreamPart |
LanguageModelV3StreamPart |
| ACP SDK | ^0.4.8 | ^0.14.1 |
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.
- 9d ago First seen · 107 lines · 43 tokens per session scan A 7729d7274c2b
release-v5-acp is a skill published in the GitHub repository mcpc-tech/mcpc (104 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 734 once invoked, about $0.0002 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
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
release-management
Tag a commit, publish a GitHub release, and read, correct or withdraw the tags and releases already there.
release-versioning
Discipline for release classification, version bumps, and changelogs, Conventional Commits classify the release range, SemVer computes the version from those commits, Keep a Changelog renders the result. Use when the user asks to cut a release, bump a version, write a changelog, decide if a change is a…
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.