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 fatihguner/foreman --skill managing-upgit clone --depth 1 https://github.com/fatihguner/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/fatihguner/foreman/managing-up)<a href="https://agentmods.dev/skills/fatihguner/foreman/managing-up"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/managing-up.svg" alt="Measured on agentmods" 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.00084 | $0.03105 |
| Opus 5 | $0.00042 | $0.01553 |
| Sonnet 5 | $0.00017 | $0.00621 |
| Haiku 4.5 | $0.00008 | $0.00311 |
Grade A, and why
managing-up 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 yesterday.
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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.
Managing Up
The most career-defining skill nobody teaches is invisible by design. Managing up -- the deliberate cultivation of a productive relationship with one's boss -- receives no curriculum in business school, no chapter in the onboarding manual, and no line item in the performance review. Yet the gap between what a leader accomplishes and what their boss perceives them as accomplishing determines promotions, resource allocation, and institutional survival more reliably than raw competence ever will. The uncomfortable truth is that talent unwitnessed is talent wasted. Effective leaders do not merely perform; they ensure the right people understand what they are performing, why it matters, and how it connects to the organisation's strategic arc.
The Framework
Managing up is not flattery, nor is it political manoeuvring. It is a structured practice built on four pillars: information management, strategic visibility, boss comprehension, and expectation calibration.
Pillar 1: Information Management -- Close the Gap
Most leaders dramatically underestimate how much information their boss needs. The assumption that a competent manager "already knows" is both common and dangerous. Bosses operate under information asymmetry by default: they manage multiple reports, navigate competing priorities, and cannot read minds. The effective leader treats upward information flow as a design problem, not an afterthought.
The information gap manifests in two directions:
- Under-reporting: Assuming the boss knows more than they do. Projects stall, problems escalate, and the boss is blindsided -- all because a direct report confused autonomy with silence.
- Over-reporting: Flooding a manager with granular detail, forcing them to extract signal from noise. This is not diligence; it is delegation of cognitive work upward.
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.
- yesterday First seen · 194 lines · 84 tokens per session scan A 02c5a2ac3787
managing-up is a skill published in the GitHub repository fatihguner/foreman (47 stars, last pushed 2d ago), licensed MIT. It adds 84 tokens to every session and 3,105 once invoked, about $0.0004 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-06.
Other skills, from other repositories
simple-man
High-compression professional communication mode. Use when the user wants fewer tokens, less reading, no filler, compact coding-agent status, terse technical answers, or low-cognitive-load collaboration without reducing effort, validation, proactivity, or accuracy.
run-difficult-conversation
Use when preparing for or facilitating a high-stakes conversation involving conflict, feedback, performance issues, or sensitive interpersonal topics.
weekly-stop-item
A weekly feedback method in which a senior leader asks one employee what the organisation should start, stop, and keep doing. It focuses especially on removing actions that create friction.
caveman
Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens"…
simple-man
High-compression professional communication mode. Use when the user wants fewer tokens, less reading, no filler, compact coding-agent status, terse technical answers, or low-cognitive-load collaboration without reducing effort, validation, proactivity, or accuracy. Do not use when the user asks for a tutorial…
simple-man
High-compression professional communication mode. Use when the user wants fewer tokens, less reading, no filler, compact coding-agent status, terse technical answers, or low-cognitive-load collaboration without reducing effort, validation, proactivity, or accuracy. Do not use when the user asks for a tutorial…