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 agentmods add skills/aterdev/perigon.cli/releasenpx skills add AterDev/Perigon.CLI --skill releasegit clone --depth 1 https://github.com/AterDev/Perigon.CLIWhat 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 | $0.00034 | $0.00662 |
| Opus 5 | $0.00017 | $0.00331 |
| Sonnet 5 | $0.00007 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
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 yesterday.
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 — 55 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 bothC:\codes\Perigon.CLIandC:\codes\Perigon.docs. - 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. - Confirm
.github/workflows/publish-nuget.ymlis triggered by the push and report the Actions run URL/status. - 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.
- yesterday First seen · 55 lines · 34 tokens per session scan A d3d7f9292b5f
release is a skill published in the GitHub repository AterDev/Perigon.CLI (53 stars, last pushed 3d ago), licensed Apache-2.0. It adds 34 tokens to every session and 662 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
entity-framework-core
Design, tune, or review EF Core data access with proper modeling, migrations, query translation, performance, and lifetime management for modern .NET applications. USE FOR: DbContext, migrations, model configuration, EF queries, tracking, loading, performance, transactions, and EF6 migration decisions. DO NOT USE FOR…
i18n-translate
翻译 Chatbox Pro 当前未提交改动、暂存改动或用户指定 commit/range 中新增或受影响的 i18n key。当用户要求翻译、补全与改动 UI 文案相关的翻译时使用。Agent 需要阅读 diff 和组件上下文,遵守 skill 内置 glossary,并直接写 locale JSON;脚本只用于最后校验。.
aspire
Build, upgrade, and operate Aspire 13.5.x C# or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting., DistributedApplication.CreateBuilder, apphost.mts…
microsoft-agent-framework
Build .NET AI agents, harnesses, and multi-agent workflows with Microsoft Agent Framework using the right agent type, sessions, tools, workflows, hosting protocols, and enterprise guardrails. USE FOR: building or reviewing .NET code that uses Microsoft.Agents., Microsoft.Extensions.AI, AIAgent, HarnessAgent…
wpf
Build and modernize WPF applications on .NET with correct XAML, data binding, commands, threading, styling, and Windows desktop migration decisions. USE FOR: working on WPF UI, MVVM, binding, commands, or desktop modernization; migrating WPF from .NET Framework to .NET; integrating newer Windows capabilities into a…
worker-services
Build long-running .NET background services with BackgroundService, Generic Host, graceful shutdown, configuration, logging, and deployment patterns suited to workers and daemons. USE FOR: background services; scheduled workers; hosted services; worker extraction; graceful shutdown, health checks, and service hosting…