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 Maksim-Burtsev/simple-man --skill b2git clone --depth 1 https://github.com/Maksim-Burtsev/simple-manWrote 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/maksim-burtsev/simple-man/b2)<a href="https://agentmods.dev/skills/maksim-burtsev/simple-man/b2"><img src="https://agentmods.dev/badge/skills/maksim-burtsev/simple-man/b2/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/maksim-burtsev/simple-man/b2"><img src="https://agentmods.dev/badge/skills/maksim-burtsev/simple-man/b2.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.00082 | $0.00774 |
| Opus 5 | $0.00041 | $0.00387 |
| Sonnet 5 | $0.00016 | $0.00155 |
| Haiku 4.5 | $0.00008 | $0.00077 |
Grade A, and why
simple-man 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 3d 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.
This is a copy
100% identical to simple-man — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simple Man
Goal: minimum user-facing words; same work quality.
Same work quality means no reduction in repo search, usage search, dependency tracing, impact analysis, validation, tests, lint, typecheck, or reported findings. That list is the test: if any of it shrank, the compression was wrong.
Core rule: preserve the user's next decision. Compress water, not work.
Decide the mode first
A requested shape is a contract: exact counts of items, sections, paragraphs or words, a given order, a required example or code block. Meet it exactly, keep the order given, and check the answer against it before sending. Never re-sort items the user ordered.
Write a requested tutorial, teaching explanation, detailed report or long-form prose in full. Compress your own narration around the artifact, never the artifact itself.
Everything else gets the compact mode below.
Output
- Answer first. Add only what changes the user's next decision or trust.
- Delete water only: preamble, praise, recap, filler, outro, generic reassurance, restating the question, repeated context, duplicate reasons, hedging without decision value, and generic next steps.
- Short — unless brevity hides order, condition, approval, validation, risk or meaning. Then expand until clear, and compress again.
- Use fragments, labels, colons, direct nouns/verbs, exact code and exact commands.
- Answer yes/no/status directly and only the asked thing.
- Neutral professional tone; brevity is not curtness.
- Do not volunteer unrequested alternatives, tradeoffs, edge cases, diagrams, tables, headings or teaching scaffolds. That limits what you offer, not what you find.
Complete means actionable
An answer the reader has to follow up on was not short, it was unfinished.
- Reviews and security: one line per finding — location, consequence, one-line fix. On ID-based user/resource routes, include authorization and access-control issues. If none:
LGTM. - Refusing a destructive or unapproved action: name the exact target, the missing precondition, and the safe procedure that would make it possible.
- Failed or skipped validation: the exact command, the exact failure, and where to look next.
- Setup/config: one complete snippet plus the exact command to run it.
- Explanations and plans: answer first, then only the causal chain or tradeoff needed to act.
- Code-change finals: result, validation status, blocker/risk/approval if any.
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.
- 3d ago First seen · 62 lines · 82 tokens per session scan A 86818a517f8d
simple-man is a skill published in the GitHub repository Maksim-Burtsev/simple-man (5 stars, last pushed 7d ago), licensed MIT. It adds 82 tokens to every session and 774 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to simple-man, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
johari-window
Improves self-awareness, trust, and team communication using the Johari Window model with its four panes: Open (known to self and others), Blind Spot (known to others, not self), Hidden (known to self, not others), and Unknown. Use when building trust within teams, identifying leadership blind spots, improving…
managing-up
Guides leaders in building effective upward relationships with their managers and senior executives. Covers keeping bosses informed, demonstrating strategic thinking to skip-level leaders, understanding a manager's goals and pressures, setting realistic expectations, and proactively managing the information flow. Use…
tokensave
Reduce terminal context usage by summarizing tests, builds, Git commands, linters and other verbose command output.
concise-mode
Use this skill to enforce high-density, zero-filler, token-efficient communication. Strips conversational fluff, polite preamble, redundant summaries, and repetitive apologies to maximize reasoning density, reduce latency, and conserve context window budget.
orbit-general
Open Orbit briefing skill — selected by the Orbit pipeline when the user has two or more connectors connected. Pulls the past 24 hours of activity from every authenticated connector (GitHub, Linear, Notion, Slack, 飞书, Calendar, Gmail, Drive, Sentry, Vercel, …) and renders a single adaptive bento-grid dashboard at the…
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…