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/docsnpx skills add AterDev/Perigon.CLI --skill docsgit 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.00067 | $0.00644 |
| Opus 5 | $0.00034 | $0.00322 |
| Sonnet 5 | $0.00013 | $0.00129 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
docs 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perigon Documentation Workflow
Workspace Scope
- The authoritative documentation lives under
Perigon.docs/Content/docs/Perigon. - Documentation is versioned by folder, then split by language:
zh-CN/<version>anden-US/<version>. - Source changes that drive Perigon docs usually come from
Perigon.CLI,Perigon.template, andPerigon.Modules.
Workflow
- Identify the affected feature, command, template behavior, module behavior, or contributor workflow.
- Check workspace changes in
Perigon.template,Perigon.CLI, andPerigon.Modulesfirst to determine what actually changed. - Ignore unrelated diffs and extract only Perigon-relevant behavior, constraints, commands, paths, version notes, or user-visible workflow changes.
- Search existing pages under
Perigon.docs/Content/docs/Perigonfor the closest matching topic before creating new content. - Prefer updating or correcting an existing document when the topic already exists.
- Create a new page only when the change introduces a clearly new concept, workflow, or reference topic.
- Keep Chinese and English docs aligned in structure and meaning. When one side changes, update the matching page in the other language unless the user explicitly asks for one language only.
- Place content in the correct version folder. If behavior differs by version, document the version-specific scope explicitly instead of silently overwriting another version's guidance.
Conventions
- Preserve the existing section taxonomy and naming style under both
zh-CNanden-US. - Keep folder symmetry when equivalent pages exist in both languages.
- Document observable behavior from the repositories, not speculation or roadmap assumptions.
- Prefer concise task-oriented guidance, with commands, paths, prerequisites, and limitations called out directly.
- When adding a new page in a section that uses
.order, update the corresponding.orderfile so navigation stays correct. - If the source change is internal only and has no user, contributor, or operator impact, do not add noise to the docs.
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 · 45 lines · 67 tokens per session scan A 898f265cf836
docs is a skill published in the GitHub repository AterDev/Perigon.CLI (53 stars, last pushed 3d ago), licensed Apache-2.0. It adds 67 tokens to every session and 644 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…