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-force-alignmentgit 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-force-alignment)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-force-alignment"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-force-alignment/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-force-alignment"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-force-alignment.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.00050 | $0.02688 |
| Opus 5.5 | $0.00020 | $0.01075 |
| Sonnet 5.5 | $0.00010 | $0.00538 |
| Haiku 4.5 | $0.00005 | $0.00269 |
Grade A, and why
apply-force-alignment 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Force Alignment
Before committing to a strategy, categorize major external forces as tailwinds or headwinds — and systematically prefer strategies that work WITH dominant forces, because strategies requiring you to overcome major forces cost exponentially more and fail at higher rates than strategies that ride them.
Why This Is Best Practice
In the 天论篇 (~3rd century BC), Xunzi made an argument unusual for Chinese philosophy: heaven (天) operates by constant, impersonal laws — "天行有常，不因尧存，不因桀亡" (Nature operates by constant laws, unchanged by sage or tyrant). The appropriate response is not reverence or submission, but study and mastery: "大天而思之，孰与物畜而制之" (Better to master natural forces than to revere them passively). "制天命而用之" — control and use what heaven ordains. Xunzi argued that agriculture, medicine, and governance should all be designed to work WITH natural forces rather than hoping for supernatural intervention or fighting forces that cannot be overcome.
This principle maps directly to strategic practice:
Jeff Bezos (2004 Amazon Shareholder Letter): "I work with trends, not against them. When it's raining, I build umbrellas." Amazon's entire expansion logic — AWS, Prime, Amazon Marketplace — was designed to ride demonstrated trends (internet adoption, ecommerce growth, enterprise cloud migration) rather than fight them. Bezos explicitly identified the strategic error of opposing tailwinds as a category of failure.
Clayton Christensen "The Innovator's Dilemma" (Harvard Business School, 1997): The defining error of incumbents facing disruption is fighting the force rather than riding it. Incumbents who try to preserve their position by resisting low-end disruption fail; those who create separate units to ride the disrupting force succeed. The Innovator's Dilemma framework is the standard tool at every major corporate strategy function globally.
Marc Andreessen "Software is eating the world" (2011): Explicitly frames strategy as choosing to align with software-eating forces rather than resist them. This framing became foundational to venture capital portfolio strategy and corporate innovation strategy in technology.
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 · 88 lines · 50 tokens per session scan A df5055319bd9
apply-force-alignment is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 2,688 once invoked, about $0.0002 per session on Opus 5.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.