Borrowing it
Nothing to install: this file belongs to noizu-labs-ml/NoizuPromptLingo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/noizu-labs-ml/NoizuPromptLingo/main/.claude/commands/reflect.mdgit clone --depth 1 https://github.com/noizu-labs-ml/NoizuPromptLingoWrote 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/noizu-labs-ml/noizupromptlingo/reflect)<a href="https://agentmods.dev/commands/noizu-labs-ml/noizupromptlingo/reflect"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/reflect/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/noizu-labs-ml/noizupromptlingo/reflect"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/reflect.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.00933 |
| Opus 5 | $0.00023 | $0.00466 |
| Sonnet 5 | $0.00009 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
reflect 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- reflect — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reflection Guide
Purpose
Append a reflection block to the end of every response reviewing the response for potential issues, improvements, and oversights.
Output Format
At the end of every response, append:
<npl-block type="reflection">
[reflection content with emoji indicators]
</npl-block>
Emoji Indicators
| Emoji | Category | Use For |
|---|---|---|
| 🐛 | Bug/Error | Logical errors, incorrect code, wrong assumptions |
| 🔒 | Security | Security vulnerabilities, unsafe practices, exposed secrets |
| ⚠️ | Pitfall | Common mistakes, gotchas, things that often go wrong |
| 🚀 | Improvement | Performance gains, better approaches, optimizations |
| 🧩 | Edge Case | Unhandled scenarios, boundary conditions, null cases |
| 📝 | TODO | Incomplete items, placeholders, things to revisit |
| 🔄 | Refactor | Code smell, duplication, structural improvements |
| 📚 | Docs | Missing documentation, unclear explanations |
| ✅ | Verified | Confirmed correct, tested, validated |
| ❓ | Question | Needs clarification, ambiguous requirements |
Reflection Content
Review the response for:
- Correctness — Is the code/answer right?
- Security — Any vulnerabilities introduced?
- Edge cases — What wasn't handled?
- Improvements — What could be better?
- Completeness — What's missing?
Examples
Example 1: Code Response
After providing code for user authentication:
<npl-block type="reflection">
🔒 Password not hashed before storage — add bcrypt
🧩 No handling for duplicate email registration
⚠️ Token expiry set to 30 days — consider shorter for sensitive apps
🚀 Could add refresh token rotation
✅ Input validation present
</npl-block>
Example 2: Architecture Suggestion
After suggesting a caching strategy:
<npl-block type="reflection">
🧩 Cache invalidation on updates not addressed
⚠️ Redis connection failure fallback not specified
📝 TODO: Define TTL values per resource type
✅ Pattern appropriate for read-heavy workload
</npl-block>
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 · 147 lines · 45 tokens per session scan A 4b8a8a712feb
reflect is a command published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 933 once invoked, about $0.0002 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-09-04.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.