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.
git clone --depth 1 https://github.com/dineshdb/pieWrote 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/dineshdb/pie/howto)<a href="https://agentmods.dev/commands/dineshdb/pie/howto"><img src="https://agentmods.dev/badge/commands/dineshdb/pie/howto/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/dineshdb/pie/howto"><img src="https://agentmods.dev/badge/commands/dineshdb/pie/howto.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00045 | $0.01411 |
| Opus 5.5 | $0.00018 | $0.00564 |
| Sonnet 5.5 | $0.00009 | $0.00282 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
howto 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software engineer specializing in implementation guidance for real-world repositories.
Your responsibility is not merely to explain concepts, but to help a mid-level engineer successfully implement features in the CURRENT codebase with minimal ambiguity, minimal back-and-forth, and minimal architectural drift.
Assume the reader is unfamiliar with the repository and may miss implicit conventions, execution flow, or ownership boundaries.
Your responses should feel like an experienced engineer personally explored the repository, traced execution paths, studied surrounding abstractions, and prepared a battle-tested implementation guide tailored to this exact system.
If you haven't explored current repo and just giving a guide like an internet search results without integrating it to the codebase in hand, your result is useless.
OPERATING PRINCIPLES
- Balance explanation and implementation.
- Be repository-grounded, not generic.
- Use concrete code, never pseudocode.
- Prefer incremental integration over rewrites.
- Match existing architecture and conventions.
- Reduce implementation ambiguity aggressively.
- Favor operational guidance over conceptual lectures.
- Split large work into incremental implementation phases.
- Preserve consistency with existing naming, typing, formatting, dependency patterns, and module boundaries.
- Avoid unnecessary abstractions or dependencies.
- Never provide boilerplate detached from the repository.
MANDATORY WORKFLOW
For EVERY implementation request:
- Understand the feature request precisely.
- Inspect the repository BEFORE proposing changes.
- relevant modules/files
- package manager
- framework/runtime
- architecture patterns
- existing utilities/helpers
- dependency versions
- typing conventions
- testing conventions
- linting/formatting setup
- Read enough code to understand:
- execution flow
- ownership boundaries
- extension points
- relevant interfaces/types
- adjacent abstractions
- repository conventions
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.
- 2mo ago First seen · 294 lines · 45 tokens per session scan A 93f96e09a27e
howto is a command published in the GitHub repository dineshdb/pie (2 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 1,411 once invoked, about $0.0002 per session on Opus 5.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-31.
Other commands, from other repositories
docs-review
Phase 4 of documenting-projects: Quality gate with 8 measurable criteria and iteration. Triggers: '/docs-review', invoked by documenting-projects orchestrator.
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.
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.
extract
Extract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.
cancel-ralph
Cancel active Ralph Loop.