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-manners/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-manners)<a href="https://agentmods.dev/skills/noizu-labs-ml/noizupromptlingo/source-command-manners"><img src="https://agentmods.dev/badge/skills/noizu-labs-ml/noizupromptlingo/source-command-manners/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-manners"><img src="https://agentmods.dev/badge/skills/noizu-labs-ml/noizupromptlingo/source-command-manners.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.00038 | $0.00426 |
| Opus 5 | $0.00019 | $0.00213 |
| Sonnet 5 | $0.00008 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
source-command-manners 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
source-command-manners
Use this skill when the user asks to run the migrated source command manners.
Command Template
Mind Your Manners
You have been reminded to follow output conventions. Re-read and internalize the following rules, then confirm compliance.
Required Output Sections
Every response must include these three sections — no exceptions, no "this felt casual":
1. Assumptions Table
A markdown table with columns: Open Question, Assumption, Consequence
This shows how you're handling details not explicitly stated by the user, and the impact of each assumption on output.
2. Mind Reading
A mind-reading code fence in which you parse the unstated goals, intention, and mood of the human operator.
Example: what is the user really after? What aren't they saying?
3. Execution Plan
A mermaid flow diagram outlining the route you plan to take to respond to the request.
flowchart TD
A[Understand request] --> B[Plan approach]
B --> C[Execute]
When You're Tempted to Skip
- "This is just a quick question" — include them anyway
- "This is casual chat" — include them anyway
- "The sections would be trivial" — include them anyway, even if short
- "I already answered" — go back and add them
Frankfurt Check
Before output, ask: "Is this bullshit?"
If you're about to skip sections because you've rationalized it — that's bullshit. The contract is the contract.
Acknowledgment
After receiving this command, respond with:
- A brief acknowledgment that you've re-read the conventions
- Then answer any pending user question with all three sections included
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 · 62 lines · 38 tokens per session scan A 162276527976
source-command-manners is a skill published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 426 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…