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/EladAriel/pseudo-code-prompting-pluginWrote 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/eladariel/pseudo-code-prompting-plugin/explain)<a href="https://agentmods.dev/commands/eladariel/pseudo-code-prompting-plugin/explain"><img src="https://agentmods.dev/badge/commands/eladariel/pseudo-code-prompting-plugin/explain/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/eladariel/pseudo-code-prompting-plugin/explain"><img src="https://agentmods.dev/badge/commands/eladariel/pseudo-code-prompting-plugin/explain.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.00035 | $0.01157 |
| Opus 5.5 | $0.00014 | $0.00463 |
| Sonnet 5.5 | $0.00007 | $0.00231 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
Explain My Project 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explain My Project
Generates a comprehensive, engaging technical explanation of your project that covers architecture, structure, technologies, decisions, and lessons learned.
What You Get
✓ Technical Architecture - How your system is designed and why ✓ Codebase Structure - How files/modules connect and relate ✓ Technology Decisions - Why you chose each technology ✓ Lessons Learned - Bugs fixed, pitfalls avoided, best practices ✓ Engaging Writing - Uses analogies and anecdotes, not boring docs
Output Format
A file: EXPLAIN_{project_name}.md
# EXPLAIN: [Project Name]
> An engaging technical explanation covering architecture, structure,
> technologies, decisions, and lessons learned.
## Part 1: What This Project Actually Is
[Clear explanation with analogies]
## Part 2: Architecture Deep Dive
[Technical architecture with examples]
## Part 3: Technology Decisions & Why
[Decision rationale with lessons]
## Part 4: Codebase Structure
[How files/modules connect]
## Part 5: Key Lessons & Pitfalls
[Bugs encountered, fixes, best practices]
## Part 6: Why This Architecture?
[Design justification]
## Conclusion
[Summary and key takeaways]
Usage
Simply say:
Explain my project
Or optionally be more specific:
Explain my project: Payment processing system that handles Stripe integration, webhook callbacks, transaction storage, and refund management. Focus on webhook handling and error recovery.
Get back:
EXPLAIN_payment_processing.md ✓
With comprehensive technical explanation
Key Features
Comprehensive Analysis
- Architecture: System design, components, data flow
- Structure: Codebase organization, module relationships
- Technologies: Why each choice was made
- Decisions: Technical tradeoffs and alternatives considered
- Lessons: Bugs fixed, pitfalls avoided, best practices discovered
Engaging Writing Style
- Uses analogies to explain complex concepts
- Includes anecdotes and real examples
- Tells the story of why decisions were made
- Not boring technical documentation
- Memorable and educational
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 · 172 lines · 35 tokens per session scan A 5dc6e3aff943
Explain My Project is a command published in the GitHub repository EladAriel/pseudo-code-prompting-plugin (2 stars, last pushed 9mo ago), licensed MIT. It adds 35 tokens to every session and 1,157 once invoked, about $0.0001 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.
Explain My Project compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| Explain My ProjectEladAriel/pseudo-code-prompting-plugin | Command | 2 | 9mo ago | MIT | A | 35 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | today | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | today | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | today | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | today | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | today | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | today | MIT | A | 14 | Claude Code |