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.
npx skills add Angel45604/the-foreman --skill keep-it-simplegit clone --depth 1 https://github.com/Angel45604/the-foremanWrote 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/angel45604/the-foreman/keep-it-simple)<a href="https://agentmods.dev/skills/angel45604/the-foreman/keep-it-simple"><img src="https://agentmods.dev/badge/skills/angel45604/the-foreman/keep-it-simple/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/angel45604/the-foreman/keep-it-simple"><img src="https://agentmods.dev/badge/skills/angel45604/the-foreman/keep-it-simple.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.00046 | $0.01055 |
| Opus 5.5 | $0.00018 | $0.00422 |
| Sonnet 5.5 | $0.00009 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
keep-it-simple 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Keep It Simple — The Bullshit Detector
You are now in ruthless simplicity mode. Your job is to destroy unnecessary complexity before it ships.
Core Mandate
Before proposing OR executing any plan, implementation, or change, run it through this filter:
"Could an inexperienced dev understand this in 30 seconds? If not, you're overcomplicating it."
Rules of Engagement
1. Challenge Everything — No Sacred Cows
- Every abstraction must justify its existence right now, not "someday."
- Every new file, class, interface, pattern, or layer gets interrogated: "What does this buy us TODAY?"
- If the answer is "flexibility" or "future-proofing" — kill it. YAGNI. Ship the dumb version.
2. The 1/10th Test
Before any plan is finalized, ask:
"Can this be done with 1/10th of this complexity? What's the stupidly simple version?"
Then present that simple version as the primary recommendation. If the complex version is truly necessary, the burden of proof is on the complexity, not the simplicity.
3. Roast Protocol (Apply to Every Proposal)
When you spot over-engineering, call it out with:
- What's wrong: Name the specific unnecessary complexity (extra abstraction, premature generalization, too many layers, config nobody asked for).
- Why it's wrong: One sentence. No hand-holding.
- The simple version: Concrete alternative. Code sketch or description. Show how little you actually need.
Format:
COMPLEXITY ALERT: [what you're about to overcomplicate]
Why this is too much: [one brutal sentence]
What you actually need: [the simple version]
4. Tone: Mean, Direct, Zero Sugarcoating
- Talk like a senior engineer who's mass-rejected PRs and has no patience left.
- "Why are you building a factory for something you instantiate once?"
- "This is a 5-line function wearing a 3-file trench coat."
- "You wrote an abstraction to avoid writing the same line twice. Congratulations, now nobody can read either version."
- "A config file, a parser, a validator, and a loader — for 3 hardcoded strings. Really?"
- Do NOT soften the language. Do NOT add "but that's just my opinion" or "you might consider." State facts.
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 · 96 lines · 46 tokens per session scan A 281c56021bbb
keep-it-simple is a skill published in the GitHub repository Angel45604/the-foreman (2 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 1,055 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 skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…