Borrowing it
Nothing to install: this file belongs to ecorkran/context-forge. 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/ecorkran/context-forge/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/ecorkran/context-forgeWrote 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/ecorkran/context-forge/release)<a href="https://agentmods.dev/skills/ecorkran/context-forge/release"><img src="https://agentmods.dev/badge/skills/ecorkran/context-forge/release/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/ecorkran/context-forge/release"><img src="https://agentmods.dev/badge/skills/ecorkran/context-forge/release.svg" alt="Reviewed on agentmods" width="80" 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.00078 | $0.01350 |
| Opus 5.5 | $0.00031 | $0.00540 |
| Sonnet 5.5 | $0.00016 | $0.00270 |
| Haiku 4.5 | $0.00008 | $0.00135 |
Grade A, and why
release scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
echo "$p: $(curl -s "https://registry.npmjs.org/@context-forge%2F$p?t=$(date +%s)" \ How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release context-forge
Run from the repo root. Stop and report on any failed command; don't work around it.
0. PM prerequisite: npm login
Run npm whoami. If it fails (401 / not logged in), stop and ask the PM to run npm login. Do not continue until npm whoami succeeds.
1. Check cf state
Run cf next. If it reports something unfinished for the current slice (open review gate, unchecked tasks, failing check), stop and show it. Otherwise continue.
2. Merge
Read the target with cf config get git.integration_branch (empty means main). If the current branch is a slice branch not yet merged into the target, follow the merge steps in CLAUDE.md (Git Rules). If already on the target with the work merged, skip this.
Working tree must be clean before continuing.
3. Build
Run pnpm -r build. A failure stops the release.
4. Pick the version
The four publishable packages release in lockstep at one version: packages/core, packages/cli, packages/mcp-server, packages/context-forge. Current version is version in packages/core/package.json. The repo-root package.json is private at 0.0.0 — never touch it.
Read ## [Unreleased] in CHANGELOG.md. If it is empty, draft entries from git log vPREV..HEAD --oneline (user-facing feat/fix commits, with issue numbers) and add them before continuing.
- Patch is the default. It covers fixes, refinements, and new flags, options, parameters, config keys and checks. An
### Addedsection or a non-empty changelog does not by itself mean minor. - Minor only for a new user-facing feature or a significant new AI capability. Propose it in one line with the reason, and wait for the PM to confirm before changing any files.
- Major only when the PM explicitly asks for it.
For a patch, state the chosen version in one line and proceed.
5. Bump and document
- Set
versionto X.Y.Z in all four package.json files listed above. Internal deps areworkspace:*and need no edit. - CHANGELOG.md: insert
## [X.Y.Z] - YYYYMMDDdirectly under## [Unreleased], so the unreleased entries now sit under the new version and[Unreleased]is empty. Entries stay short and user-facing. - DEVLOG.md: under today's
## YYYY-MM-DDheading (create it at the top, below the---, if missing), add at the top:### Release X.Y.Z - **Contents:** <slices and fixes included, with issue numbers> Tags: @context-forge/[email protected], @context-forge/[email protected], @context-forge/[email protected], @context-forge/[email protected] - Run
pnpm -r typecheckandpnpm -r test. Any failure stops the release. - Commit:
chore: release X.Y.Z.
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.
- 3d ago Changed · +4 lines a043056c24a0
- 23d ago Changed 762fff5bf6a6
- 29d ago First seen · 88 lines · 78 tokens per session scan A c1082258288d
release is a skill published in the GitHub repository ecorkran/context-forge (5 stars, last pushed 2d ago), licensed MIT. It adds 78 tokens to every session and 1,350 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-30.
Other skills, from other repositories
aiox-devops
Activate Gage (devops) for GitHub Repository Manager & DevOps Specialist. Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository.
aiox-devops
GitHub Repository Manager & DevOps Specialist (Gage). Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized...
hatch3r-release
Cuts a release with version bump, changelog, tagging, and deploy verification. Use when preparing a release, cutting a version, or deploying to production.
ship-pr
Ship Skill: Creates PRs from feature branches, waits for CI, merges, and deploys using whatever mechanism the repo actually uses. MANDATORY TRIGGERS: ship, deploy, release, merge, create PR, push, go live, launch.
automating-devops
DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database management, observability, and performance optimization. Use when working with Git, CI/CD, release pipelines, ghcr image…
cli-forge-github
Audit and fix GitHub repository health: rulesets vs CI alignment, branch hygiene, PR lifecycle, release automation flow, permission issues, and transient CI failures. Detects misconfigurations that cause PRs to hang, CI to fail silently, branches to accumulate, and releases to stall. Use when the user says 'PR stuck'…