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 parisgroup-ai/imersao-ia-setup --skill project-releasegit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/parisgroup-ai/imersao-ia-setup/project-release)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/project-release"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/project-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/parisgroup-ai/imersao-ia-setup/project-release"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/project-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.00023 | $0.02959 |
| Opus 5 | $0.00012 | $0.01479 |
| Sonnet 5 | $0.00005 | $0.00592 |
| Haiku 4.5 | $0.00002 | $0.00296 |
Grade A, and why
project-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 11d 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.
curl -s https://app.example.com/api/health | head -20 How it starts
The opening of the file, as written. The whole thing — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Release
Release workflow for monorepo projects that deploy via push-to-main (Railway, Vercel, Render, Fly.io, etc). Handles quality gates, version bump, changelog generation, git tagging, and push.
Unlike /release-maintenance (which publishes npm packages to a registry), this skill deploys apps — web frontends, API servers, background workers, mobile OTA updates.
Usage
/project-release # Full release (auto-detect changes)
/project-release patch # Force patch bump
/project-release minor # Force minor bump
/project-release major # Force major bump (requires confirmation)
/project-release --dry-run # Show what would happen without executing
/project-release --hotfix "desc" # Minimal release: skip changelog, fast-track
Parse Arguments
Extract from: {{ARGUMENTS}}
If ARGS is empty → MODE = auto (detect bump from commits)
If ARGS is patch|minor|major → MODE = forced bump
If ARGS has --dry-run → MODE = dry-run
If ARGS has --hotfix → MODE = hotfix
Pipeline Overview
┌─────────────────────────────────────────────────────────────────┐
│ 1. PRE-FLIGHT Gather state, detect changes │
│ 2. QUALITY GATES type-check, lint, tests │
│ 3. VERSION BUMP Determine + apply new version │
│ 4. CHANGELOG Generate from conventional commits │
│ 5. COMMIT + TAG Atomic release commit with tag │
│ 6. PUSH Triggers deployment automatically │
│ 7. VERIFY Monitor deployment health │
└─────────────────────────────────────────────────────────────────┘
Step 1: PRE-FLIGHT — Gather State
Run these in parallel to build a complete picture:
# Current version
cat package.json | grep '"version"'
# Last release tag
git tag -l 'v*' --sort=-version:refname | head -1
# Commits since last tag (or all if no tags)
git log $(git tag -l 'v*' --sort=-version:refname | head -1)..HEAD --oneline 2>/dev/null \
|| git log --oneline -30
# Working tree status
git status --short
# Branch check
git branch --show-current
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.
- 11d ago First seen · 393 lines · 23 tokens per session scan A a40f71b3e007
project-release is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 28d ago), licensed MIT. It adds 23 tokens to every session and 2,959 once invoked, about $0.0001 per session on Opus 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-08-31.
Other skills, from other repositories
pr-release
Generate changelog entries, a deployment checklist, and update a release PR description. Invoke when user asks to prepare a release, generate a changelog, create a deployment checklist, or uses /pr-release. Requires user confirmation before updating the PR (modifies publicly visible content). Supports version numbers…
drupal-mr
Create or list merge requests for drupal.org projects via git.drupalcode.org. Invoke when user wants to create a merge request for a drupal.org issue, says "create a drupal.org MR", "set up a merge request for issue", or uses /drupal-mr. Has side effects: clones repos to /.cache/drupal-contrib/ and pushes to…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
deliver-release-notes
Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.