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 ecorkran/context-forge --skill setup-cigit 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/setup-ci)<a href="https://agentmods.dev/skills/ecorkran/context-forge/setup-ci"><img src="https://agentmods.dev/badge/skills/ecorkran/context-forge/setup-ci/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/setup-ci"><img src="https://agentmods.dev/badge/skills/ecorkran/context-forge/setup-ci.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.00113 | $0.02737 |
| Opus 5.5 | $0.00045 | $0.01095 |
| Sonnet 5.5 | $0.00023 | $0.00547 |
| Haiku 4.5 | $0.00011 | $0.00274 |
Grade A, and why
setup-ci 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 today.
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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: setup-ci description: Set up CI for a project, and offer to generate its own /release skill. Detects the stack, writes .github/workflows/ci.yml from the guide's baseline and generates the project's own .claude/skills/release/SKILL.md (release process: version bump, tag, CI watch, registry check). Use when the user says "set up CI", "add a release skill", "add a release process", "set up releases", or when a project has no .github/workflows/ci.yml or release skill.
Set up CI and release
Run from the project root. Detect first, ask only about what can't be detected, then write two files. Both belong to the project afterward and are edited by hand. This skill does not maintain them.
Baselines live in the guide at project-documents/ai-project-guide/project-guides/ci/<lang>/ci.yml (python, typescript). If the stack is another language, say there is no baseline yet and stop. Do not improvise one.
If .github/workflows/ci.yml or .claude/skills/release/SKILL.md already exists, show what exists and ask before overwriting either.
1. Detect
| Slot | How |
|---|---|
| Language | pyproject.toml means python; package.json plus tsconfig.json means typescript |
| Version files | Grep the current version string in pyproject.toml, package.json, __init__.py/_version.py, and the project's other manifests and source files. Skip the changelog, the devlog and project-documents/: they record versions rather than define them. List every remaining hit. |
| Lock refresh | python: uv lock if uv.lock exists. npm: npm install --package-lock-only; pnpm: pnpm install --lockfile-only. None if no lockfile. |
| Tag format | git tag --sort=-creatordate | head. Copy the pattern (v1.2.3, 1.2.3). No tags: vX.Y.Z. |
| Tag | <tag> in the release skill: the tag format written with the literal placeholder X.Y.Z (so vX.Y.Z or X.Y.Z). The release fills in the real number at release time. |
| Changelog | CHANGELOG.md (check the root, then docs/). Note whether it has ## [Unreleased]. None: the release skill skips the changelog step. |
| Devlog | DEVLOG.md at the root only. Ignore any other devlog, including project-documents/DEVLOG.md. None at the root: skip the devlog step without asking. |
| Publish target | An existing publish job in a workflow, else the manifest: python [project] name means PyPI; package.json without "private": true means npm. Private or no manifest name: none. |
| Package name | name from the manifest. It can differ from the repo name. |
| Project | <project> in the release skill: the package name, or the repo directory name when there is none. |
| Registry | <registry> in the release skill: PyPI or npm, from the publish target. None: the [registry] text is removed. |
| Registry check | PyPI: https://pypi.org/pypi/<pkg>/<ver>/json. npm: npm view <pkg>@<ver> version. None: the release stops at green CI. |
| Python versions | Every minor listed in the Programming Language :: Python :: 3.N trove classifiers, as a quoted YAML list. No classifiers: every minor from the requires-python floor through its upper bound. No upper bound, or no requires-python: ask. Never fill the top of the range from memory. |
| Node versions | The majors engines.node allows, as a quoted YAML list. If engines.node is missing or has no upper bound, ask which majors to test. Never fill the range from memory. |
| Publish runtime | __PUBLISH_PYTHON_VERSION__ / __PUBLISH_NODE_VERSION__: the lowest version in the matrix. |
| Tag glob | __TAG_GLOB__, derived from the tag format: v* for v-prefixed tags, [0-9]* for bare ones. |
| Commit type | <commit type> in the release skill: package if the project uses the guide's commit types, else chore. |
| Check commands | python: ruff check, ruff format --check, pyright (or the project's type checker), pytest. typescript: the lint, typecheck, test, build scripts in package.json. Fill __*_SCRIPT__ only with scripts that exist. If one is missing, say so and drop that step rather than inventing it. |
| Integration branch | cf config get git.integration_branch, only to fill the CI trigger branches (main, plus this value if set). Never bake it into the release skill. |
| cf project | Does cf exist and does project-documents/ exist? Decides whether the release skill keeps the cf steps. |
| Frontmatter block | Enable the OPTIONAL cf block in ci.yml when project-documents/ exists and its markdown files carry YAML frontmatter. Otherwise remove it. |
| Fetch main | Enable the OPTIONAL git fetch origin main:main line when any test file reads main from the project's own checkout: origin/main, a main.. range, or --diff main and similar ref arguments. A branch named main in a temporary repo the test creates itself (git init -b main) does not count. Tag builds go red without it. No such reference: remove it. Unsure: ask. |
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.
- today First seen · 133 lines · 0 tokens per session scan A 9cbfac042c7f
setup-ci is a skill published in the GitHub repository ecorkran/context-forge (5 stars, last pushed yesterday), licensed MIT. It adds 113 tokens to every session and 2,737 once invoked, about $0.0005 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-10-17.
Other skills, from other repositories
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.
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'…
metagit-release-audit
Mandatory before calling work complete when the session changed repo files. Runs format, lint, tests, integration tests, context-aware pip-audit/bandit, and optional gitleaks via task qa:prepush. Use before push, release, or hand-off.
github-ops
GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git…
github
Full-featured GitHub integration via the gh CLI. Manage repositories, issues, pull requests, CI/CD workflows, releases, and make raw API calls.