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 commands/principle-labs/corivo/_conventionsgit clone --depth 1 https://github.com/Principle-Labs/CorivoWrote 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/commands/principle-labs/corivo/_conventions)<a href="https://agentmods.dev/commands/principle-labs/corivo/_conventions"><img src="https://agentmods.dev/badge/commands/principle-labs/corivo/_conventions.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.00250 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
_conventions 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 5d 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.
What it actually says
Command Conventions
These command files are prompt templates for Codex app slash commands. Keep them deterministic and operationally useful.
Required Sections
Every command file in this plugin should include:
PreflightPlanCommandsVerificationSummaryNext Steps
Frontmatter
Every command file needs YAML frontmatter with a description field:
---
description: One-line summary of what the command does.
---
Command Style
- Prefer
corivoCLI commands over ad-hoc shell logic. - Always check whether
corivois installed and initialized before performing writes or reads. - Do not add password-related CLI flags to non-interactive flows.
- Avoid echoing sensitive content such as secrets or raw private data unless the user asked for it.
- If a command writes memory, show the proposed annotation before executing the save.
Naming
- Store user-invocable command files directly under
commands/. - Files prefixed with
_are documentation-only and should not be treated as commands. - Assume Codex will expose these commands with the plugin prefix, for example
/corivo:status.
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.
- 5d ago First seen · 39 lines · 0 tokens per session scan A 908d5f871b17
_conventions is a command published in the GitHub repository Principle-Labs/Corivo (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 250 tokens. 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-31.
Other commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
commit
智能生成 Git 提交信息并提交.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
create-issue
Transform feature descriptions, bug reports, or improvement ideas into well-structured GitHub issues.