Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/AterDev/Perigon.CLInpx agentmods add skills/aterdev/perigon.cli/releaseWrote 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/aterdev/perigon.cli/release)<a href="https://agentmods.dev/skills/aterdev/perigon.cli/release"><img src="https://agentmods.dev/badge/skills/aterdev/perigon.cli/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/aterdev/perigon.cli/release"><img src="https://agentmods.dev/badge/skills/aterdev/perigon.cli/release.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.00034 | $0.00629 |
| Opus 5.5 | $0.00014 | $0.00252 |
| Sonnet 5.5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
release 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perigon.CLI Release Workflow
Use this skill when releasing Perigon.CLI or when the user asks to package and publish a version. The NuGet publishing workflow runs automatically when origin/nuget receives a push.
Before editing
- Inspect
git statusin bothPerigon.CLIandPerigon.docsrepositories. - Preserve unrelated user changes. Stage only files belonging to the release.
- Confirm the exact current version from
src/Apps/CommandLine/CommandLine.csproj.
Release contents
- Unless the user specifies a version, increment only the patch component of
<Version>insrc/Apps/CommandLine/CommandLine.csproj. - Keep
src/Apps/Dashboard/Dashboard.csprojon the same version. - Update
<PackageReleaseNotes>with only the changes being released. - Update the matching Chinese and English pages under
Perigon.docs/Content/docs/Perigon, normally the command-line page and the version update notes. Keep their structure and meaning aligned. - Add or update reusable release guidance in this skill and
Contribution.mdwhen the workflow changes.
Validation
Run the focused tests for the changed feature, then the full test project:
dotnet test tests/StudioMod.Tests/CoreMod.Tests.csproj --configuration Release --verbosity minimal
The CI-equivalent package/studio build is:
pwsh ./scripts/PublishToLocal.ps1 -withStudio:$true
PublishToLocal.ps1 reads the tracked src/Apps/CommandLine/ShareDlls.txt when packaging Studio and removes the listed duplicate DLLs. If project dependencies change, run scripts/CheckSharedDlls.ps1 to refresh the list and commit the updated file.
Run it only after tests pass; it creates local publish/package artifacts and may install the package locally.
Branch handoff
- Commit the Perigon.CLI release changes on the current development branch with a conventional emoji-prefixed message such as
🚀 release: prepare Perigon.CLI 10.1.12. - Push that branch if it is the requested source branch.
- Fetch
origin/nuget, verify it has no unexpected divergence, merge the release commit into a localnugetbranch, and pushnugetwithout force-pushing. - add git tag
v<version>to the release commit and push the tag.
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.
- 1mo ago Changed · -1 lines 3f3e093427e6
- 1mo ago First seen · 55 lines · 34 tokens per session scan A d3d7f9292b5f
release is a skill published in the GitHub repository AterDev/Perigon.CLI (54 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 629 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
bump-version
Bump the SSW.VerticalSliceArchitecture.Template NuGet package version to cut a new release. Use when the user says "bump the version", "cut a release", "release a new version", "publish a new package version", or similar for this template repo. Edits the version in VerticalSliceArchitecture.nuspec — which is what…
maf-release-watcher
Detects new MAF releases and keeps the registry, matrix and guides current. Pipeline: (1) the watcher diffs every tracked package surface and opens a scaffold PR on a per-version branch, (2) the maf-registry-fill agentic workflow fills the TODOs inside Actions, (3) required PR gates decide; releases without breaking…
release-notes
Generate release notes from git history and CHANGELOG. Formats for GitHub Release, Slack, or email. Use before tagging a release.
versioning-policy
SemVer rules for Squad's stable, preview, insider, and local package versions.
changelog
Auto-generate changelog from git commits — grouped by feat/fix/docs with PR links.
fork-and-publish-skill
Customizes an installed agent skill and ships it back upstream or as a versioned fork using qvr's edit/publish authoring loop. Use when a user wants to modify, customize, fork, release, or publish a qvr skill — e.g. "edit this skill", "publish my changes", "fork a skill to my own repo", "cut a v1.0.0 release of a…