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 human-avatar/skills-for-humanity --skill s4h-resource-leverage-mappinggit clone --depth 1 https://github.com/human-avatar/skills-for-humanityWrote 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/human-avatar/skills-for-humanity/s4h-resource-leverage-mapping)<a href="https://agentmods.dev/skills/human-avatar/skills-for-humanity/s4h-resource-leverage-mapping"><img src="https://agentmods.dev/badge/skills/human-avatar/skills-for-humanity/s4h-resource-leverage-mapping/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/human-avatar/skills-for-humanity/s4h-resource-leverage-mapping"><img src="https://agentmods.dev/badge/skills/human-avatar/skills-for-humanity/s4h-resource-leverage-mapping.svg" alt="Reviewed on agentmods" width="80" 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.00059 | $0.01136 |
| Opus 5 | $0.00030 | $0.00568 |
| Sonnet 5 | $0.00012 | $0.00227 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
s4h-resource-leverage-mapping 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 9d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resource Leverage Mapping
Not all uses of a resource are equal. Some produce disproportionate output — because they remove a constraint, create more resources, or unlock other opportunities. Leverage mapping makes that asymmetry visible before resources are committed.
Your Process
Step 1: Inventory Available Resources List all meaningful resources available: time, money, people, attention, relationships, existing assets, reputation. Be specific — "the engineering team" is less useful than "three senior engineers with 20% slack capacity."
Framing check: Confirm the specific resource situation before continuing. State what you've identified — the context, the resources in scope, and the allocation question being asked — in one sentence, then use AskUserQuestion:
- Question: "I'm reading this as: [your one-sentence framing of the resource situation and the core allocation question]. Is that right?"
- Header: "Framing"
- Options:
- Yes — proceed — framing is correct
- Adjust — one element is off; user will correct it before you continue
- Reframe — different situation than read; incorporate the correction before proceeding
Step 2: List All Candidate Uses For each resource, what are all the plausible ways it could be deployed? Do not filter yet — generate a full list of options.
Step 3: Estimate Output per Unit of Input For each candidate use: what is the likely output for a given unit of input? This doesn't need to be precise — a rough order-of-magnitude estimate is sufficient. The goal is to find the outliers.
Step 4: Identify Multiplier Effects Which uses of a resource create more resources, unlock additional capacity, or enable other uses? These are the highest-leverage options. Examples: building a relationship that opens a distribution channel; shipping a feature that funds the next two.
Step 5: Find Underused High-Leverage Resources Which available resources are currently underused relative to their potential leverage? Relationships, existing data, attention from a key person, and existing assets are commonly overlooked.
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.
- 9d ago First seen · 101 lines · 59 tokens per session scan A 823850d49b0a
s4h-resource-leverage-mapping is a skill published in the GitHub repository human-avatar/skills-for-humanity (223 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,136 once invoked, about $0.0003 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-03.
Other skills, from other repositories
decision-making-under-pressure
Provides practical habits for making better decisions faster -- reframing problems before solving them, knowing when to stop deliberating, balancing intuition with analysis, resisting 'just this once' compromises, and breaking overthinking cycles. Use when facing a high-stakes choice with incomplete data, sensing that…
flow-state
Optimizes individual and team productivity using Csikszentmihalyi's flow state framework, covering the conditions for flow (clear goals, immediate feedback, challenge-skill balance), the four-stage flow cycle, and organizational flow design. Use when auditing personal or team focus time, diagnosing productivity loss…
woop
Turn wishes into action plans using mental contrasting: Wish → Outcome → Obstacle → Plan.
the-eisenhower-matrix
Prioritize tasks by urgency and importance into Do, Schedule, Delegate, Eliminate.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
recipe-add-integration-tests
Add integration/E2E tests to existing codebase using Design Docs.