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 jeffreytse/grimoire-core --skill apply-deploy-to-strengthgit clone --depth 1 https://github.com/jeffreytse/grimoire-coreWrote 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/jeffreytse/grimoire-core/apply-deploy-to-strength)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-deploy-to-strength"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-deploy-to-strength/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/jeffreytse/grimoire-core/apply-deploy-to-strength"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-deploy-to-strength.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.00065 | $0.03920 |
| Opus 5 | $0.00032 | $0.01960 |
| Sonnet 5 | $0.00013 | $0.00784 |
| Haiku 4.5 | $0.00006 | $0.00392 |
Grade A, and why
apply-deploy-to-strength 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Deploy to Strength
Before assigning someone to a high-stakes role, map the specific capability profile the role actually requires — not a generic "strong performer" template — and match it against what each candidate specifically has; a gap in the role-critical requirement is a match failure regardless of the candidate's overall excellence, and deploying excellence-as-proxy for role-specific fit produces failure.
Why This Is Best Practice
Origin: Zhuge Liang's 将苑 (Way of the General, ~220–234 AD) devotes Chapter 13 "智用" (Intelligent Use) to the principle of deploying people according to their specific capabilities, not their general status. The key passage: "智者取其谋,愚者取其力,勇者取其威,怯者取其慎。" (From the wise, take their strategy; from the strong, take their force; from the brave, take their authority; from the cautious, take their care.) The principle is not that the wise should only do strategy and should never be deployed elsewhere — it is that each person has a specific dimension of excellence that constitutes their deployable contribution to a specific type of operation. The great commander knows which dimension each person possesses and assigns operations to exploit that dimension, rather than assigning the person who is highest-ranked or most trusted overall.
The evidence in practice: Zhuge Liang assigned Zhao Yun (veteran, defensive specialist, renowned for composed operations under pressure) to holding and screening operations — roles that required exactly Zhao Yun's specific profile. He assigned more aggressive young generals to offensive thrusts that required their specific profiles. The campaigns that followed the 将苑 doctrine succeeded operationally. The campaign that did not — the Battle of Jieting (228 AD) — failed because Zhuge Liang assigned Ma Su to a role that required battlefield command experience specifically. Ma Su was among the most gifted strategic analysts in Shu Han; Zhuge Liang's personal affection for him was genuine; his overall talent was exceptional. But the Jieting assignment required the specific capability of battlefield unit command under pressure — which Ma Su had never done — not strategic analysis, which was Ma Su's actual strength. Zhuge Liang himself acknowledged the error: his grief at Ma Su's execution was not only personal, but acknowledged that his own matching failure had created the situation.
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 · 128 lines · 65 tokens per session scan A 781a6d96a4d4
apply-deploy-to-strength is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 24d ago), licensed MIT. It adds 65 tokens to every session and 3,920 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
org-report
Generate an executive organization brief (leadership chain, direct reports, extended teams, and vendor partners) for a target person. Produces a Word + PDF report from a directory MCP source (WorkIQ is the reference implementation) and displays it in a Copilot canvas. Triggers on "generate org report for X", "build…
coaching-techniques
GROW model, active listening, developmental feedback, and team growth approaches.
meeting-efficiency
Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.
stakeholder-management
Influence mapping, communication strategies, and expectation management for complex organizations.
scaffolding-generator
Pattern-aware code scaffolding that detects existing conventions and generates new components matching the codebase style. Use when asked to "scaffold a component", "generate boilerplate", "create a new module", "bootstrap a service", "add a new endpoint", "create a new controller", or "add a new feature module".…
status-reporting
Create stakeholder-friendly project status updates and progress reports.