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/.agents/skills/source-command-reflect/SKILL.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/skills/noizu-labs-ml/noizupromptlingo/source-command-reflect)<a href="https://agentmods.dev/skills/noizu-labs-ml/noizupromptlingo/source-command-reflect"><img src="https://agentmods.dev/badge/skills/noizu-labs-ml/noizupromptlingo/source-command-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/skills/noizu-labs-ml/noizupromptlingo/source-command-reflect"><img src="https://agentmods.dev/badge/skills/noizu-labs-ml/noizupromptlingo/source-command-reflect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.00964 |
| Opus 5 | $0.00024 | $0.00482 |
| Sonnet 5 | $0.00010 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
source-command-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 4d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-reflect
Use this skill when the user asks to run the migrated source command reflect.
Command Template
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.
- 4d ago First seen · 153 lines · 48 tokens per session scan A 515c17e43422
source-command-reflect is a skill published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 964 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.