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 modest-curator478/claude-skills --skill managing-upgit clone --depth 1 https://github.com/modest-curator478/claude-skillsWrote 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/modest-curator478/claude-skills/managing-up)<a href="https://agentmods.dev/skills/modest-curator478/claude-skills/managing-up"><img src="https://agentmods.dev/badge/skills/modest-curator478/claude-skills/managing-up/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/modest-curator478/claude-skills/managing-up"><img src="https://agentmods.dev/badge/skills/modest-curator478/claude-skills/managing-up.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.00242 | $0.02884 |
| Opus 5 | $0.00121 | $0.01442 |
| Sonnet 5 | $0.00048 | $0.00577 |
| Haiku 4.5 | $0.00024 | $0.00288 |
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 11d 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 managing-up — 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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing Up: Building the Relationship That Earns Autonomy
This skill addresses the relationship between a Director-level demand gen or RevOps leader and the person they report to: a CEO, CRO, VP of Marketing, or other executive. The goal is not to manage around the manager. The goal is to build enough trust and communication quality that the manager stops needing to manage closely, because they have confidence in what is happening and what will happen.
Most friction in the upward relationship is a communication problem, not a competence problem. The manager micromanages because they are uncertain. They change priorities because they do not trust that the current priorities are right. They get pulled into details because they have not seen evidence that the details are being handled. Fixing the communication often fixes the relationship.
This skill does not assume the manager is right and the practitioner is wrong. Sometimes the directive is genuinely bad. Sometimes the manager does not understand the function well enough to evaluate the program. This skill addresses both situations: how to work effectively with a good manager and how to professionally push back on a bad directive.
HOW TO SET UP THIS SKILL
Provide:
- Who you report to: CEO, CRO, VP of Marketing, or other
- How long the relationship has existed
- The specific friction or challenge: micromanagement, changing priorities, disagreement on strategy, lack of autonomy, or something else
- Whether this is a new relationship you want to start well, or an existing relationship you need to repair or improve
- What you have already tried
Diagnosing the Type of Upward Friction
Type 1: The manager who does not understand the function
A CEO or CRO who came up through sales often does not have a practitioner's understanding of demand gen or RevOps. They know what they want the function to produce (pipeline, revenue, data clarity) but not how it works. This produces friction when they give directives that are technically wrong, question decisions that are correct, or set expectations that are disconnected from how long things actually take.
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.
- 11d ago First seen · 330 lines · 242 tokens per session scan A e817e9a8bac8
managing-up is a skill published in the GitHub repository modest-curator478/claude-skills (4 stars, last pushed today), licensed MIT. It adds 242 tokens to every session and 2,884 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to managing-up, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
n8n
N8N Documentation - Workflow automation platform with AI capabilities.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
accint-commitments
Triage acc's open promises and close them with honest real-world verdicts via accact(runtime="outcome").
peon-ping-toggle
Toggle peon-ping sound notifications on/off. Use when user wants to mute, unmute, pause, or resume peon sounds during a Claude Code session. Also handles config changes like volume, pack rotation, categories — any peon-ping setting.
TEMPLATE
../../../agents/personas/TEMPLATE.md.
cao-session-management
Interact with CAO (CLI Agent Orchestrator) — launch multi-agent sessions, check status, send follow-up instructions, unblock stuck terminals, or shut down sessions. Use when working with CAO sessions in any capacity.