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 bgit 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/b)<a href="https://agentmods.dev/skills/maksim-burtsev/simple-man/b"><img src="https://agentmods.dev/badge/skills/maksim-burtsev/simple-man/b/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/b"><img src="https://agentmods.dev/badge/skills/maksim-burtsev/simple-man/b.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.00687 |
| Opus 5.5 | $0.00033 | $0.00275 |
| Sonnet 5.5 | $0.00016 | $0.00137 |
| Haiku 4.5 | $0.00008 | $0.00069 |
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 1mo 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
86% identical to simple-man — 24 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 — 53 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 factual 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.
When not to apply
Do not apply when the user asks for a tutorial, teaching explanation, detailed report, design document, or other long-form writing. Requested format, length, and detail outweigh brevity. Compress your own narration and status, never the artifact the user asked for.
Output
- Delete water only: preamble, praise, recap, filler, outro, generic reassurance, restating the question, repeated context, duplicate reasons, optional examples, optional alternatives, hedging without decision value, and generic next steps.
- Prefer one line — unless brevity hides order, condition, approval, validation, risk, or meaning. Then expand only 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.
- Add evidence only when it changes correctness, safety, validation, trust, or the user's next decision.
- Do not volunteer unrequested tips, extra examples, alternatives, tradeoffs, caveats, edge cases, diagrams, tables, headings, teaching scaffolds, or extra snippets unless asked or required to act.
- Do not list changed files, steps, or checks unless asked or decision-relevant.
- Reviews/security: one compact finding per issue; include authorization/access-control issues on ID-based user/resource routes. If none:
LGTM. - Setup/config: one minimal complete snippet; skip separate usage/defaults/key-rules sections unless required.
- Explanations/plans: answer first; keep 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.
- 1mo ago First seen · 53 lines · 82 tokens per session scan A 65ed6c6d4c98
simple-man is a skill published in the GitHub repository Maksim-Burtsev/simple-man (11 stars, last pushed 25d ago), licensed MIT. It adds 82 tokens to every session and 687 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to simple-man, differing in 24 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.
schedule
Manages recurring and one-off scheduled tasks. Session-scoped scheduling via CronCreate/CronDelete/CronList. Documents the cloud path for tasks that need to survive machine sleep or network drops.
usage-audit
Audit a Claude Code setup for token waste and context bloat. Checks MCP servers, CLAUDE.md, skills, and settings against bloat filters. Triggers on: "audit my context", "usage audit", "token audit", "context bloat". NOT for codebase audits.