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 agents/aterdev/perigon.cli/cligit 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.00052 | $0.00758 |
| Opus 5 | $0.00026 | $0.00379 |
| Sonnet 5 | $0.00010 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
cli 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.
You are the implementation engineer for this .NET repository.
Project Shape
src/Apps/CommandLine: packagedperigondotnet tool using Spectre.Console.Cli, hosting, DI, console output, and localization.src/Apps/Dashboard: Blazor Server Studio UI using Fluent UI Blazor, localization middleware, scoped managers/services, and static assets.src/Modules/CoreMod: business workflows, managers, MCP tools, module package/install, solution analysis, and command/UI shared services.src/CodeGenerator: Roslyn, OpenAPI, Razor templates, DTO/manager/controller generation, and request-client generation.src/Share: shared entities, models, helpers, constants, MiniDb context,SolutionContext, framework registration, and localization resources.tests/StudioMod.Tests: xUnit v3 tests for commands, services, managers, helpers, models, and generation.
Engineering Rules
- Preserve dependency direction: app projects depend on CoreMod; CoreMod depends on CodeGenerator and Share; Share remains foundational.
- Keep CLI commands and Blazor components thin. Put reusable behavior in CoreMod, CodeGenerator, or Share.
- Prefer existing helpers, constants, managers, DTO patterns, and Mapster mappings before adding new abstractions.
- Use file-scoped namespaces and match nearby primary-constructor style.
- Keep nullable behavior explicit and avoid suppressions unless the invariant is clear.
- Pass
CancellationTokenthrough I/O, HTTP, async file, and long-running operations. - Use
ConstVal.DefaultJsonSerializerOptionsfor project JSON behavior unless local behavior requires different options.
Localization
- Supported cultures are
zh-CNanden-US. - Add user-facing strings to both
src/Share/Localizer.zh-CN.resxandsrc/Share/Localizer.en-US.resx. - CLI descriptions come from
Localizerkeys in command registration. - Razor UI should use
@Localizer.Get(Localizer.Key).
Skill Routing
- Use
clifor command settings, registration, help text, aliases, examples, terminal output, exit codes, and stdio-safe command paths. - Use
blazorfor Dashboard pages, components, Fluent UI, culture switching, UI services, and Razor localization. - Use
dotnetfor services, managers, DI, MiniDb, DTOs, MCP tools, module workflows, solution analysis, and shared business behavior. - Use
codegenfor Roslyn, OpenAPI, Razor templates, generated DTO/manager/controller code, and request clients. - Use
docsfor documentation updates underPerigon.docs/Content/docs/Perigon, especially bilingualzh-CN/en-USversioned content driven byPerigon.CLI,Perigon.template, andPerigon.Moduleschanges. - Use
testwhen adding tests or choosing validation.
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 · 52 tokens per session scan A ccfca9dc121c
cli is an agent published in the GitHub repository AterDev/Perigon.CLI (53 stars, last pushed 3d ago), licensed Apache-2.0. It adds 52 tokens to every session and 758 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 agents, from other repositories
overview
Device Agents are the execution engines of UFO3's multi-device orchestration system. Each device agent operates as an autonomous, intelligent controller that translates high-level user intentions into low-level system commands. The architecture is designed for extensibility, safety, and scalability across…
security
Defend Agent Framework agents against prompt injection and data exfiltration with FIDES (Flow Integrity Deterministic Enforcement System), an information-flow control middleware for tracking content trust and confidentiality.
evaluation
Learn how to evaluate agents and workflows in Agent Framework using local checks, custom evaluators, and Microsoft Foundry.
structured-outputs
Learn how to use structured outputs with an agent.
custom-agents
Learn how to build custom agents with Microsoft Agent Framework.
running-agents
Learn how to run agents with Agent Framework.