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/testnpx skills add AterDev/Perigon.CLI --skill testgit 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.00061 | $0.00351 |
| Opus 5 | $0.00030 | $0.00176 |
| Sonnet 5 | $0.00012 | $0.00070 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
test 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.
What it actually says
Test And Validation
Test Placement
- CLI behavior:
tests/StudioMod.Tests/Commands - Core services:
tests/StudioMod.Tests/Services - Managers and MiniDb behavior:
tests/StudioMod.Tests/Managers - Code generation and OpenAPI/request clients:
tests/StudioMod.Tests/Generate - Roslyn, parsing, conversion, assembly, and utilities:
tests/StudioMod.Tests/Helper - Shared model behavior:
tests/StudioMod.Tests/Models
Conventions
- Use xUnit v3
[Fact],[Theory], and[InlineData]. - Use Moq when simple stubs are not enough.
- Stub HTTP with local
HttpMessageHandler; tests must not hit live endpoints. - Use unique temp directories for file-system tests and restore current directory in
finally. - Isolate MiniDb paths and avoid shared persistent state.
- Keep tests focused on observable behavior and regression risk.
- For generated code, assert meaningful snippets or structural markers instead of large snapshots unless exact text is the contract.
Validation Policy
- Metadata-only changes usually need path/frontmatter inspection, not a build.
- Narrow behavior changes should get targeted tests for the affected area.
- Broad cross-layer changes may justify targeted tests plus diagnostics or a build.
- Avoid full solution builds unless the user asks or risk justifies the time.
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 · 33 lines · 61 tokens per session scan A bfaf24066f04
test is a skill published in the GitHub repository AterDev/Perigon.CLI (53 stars, last pushed 3d ago), licensed Apache-2.0. It adds 61 tokens to every session and 351 once invoked, about $0.0003 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
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…
azure-functions
Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns. USE FOR: working on Azure Functions in .NET; migrating from the in-process model to the isolated worker model; adding Durable Functions, bindings, or host configuration.…
maui
Build, review, or migrate .NET MAUI applications across Android, iOS, macOS, and Windows with correct cross-platform UI, platform integration, and native packaging assumptions. USE FOR: working on cross-platform mobile or desktop UI in .NET MAUI; integrating device capabilities, navigation, or platform-specific code…