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-emergent-scalinggit 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-emergent-scaling)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-emergent-scaling"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-emergent-scaling/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-emergent-scaling"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-emergent-scaling.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.00092 | $0.01997 |
| Opus 5.5 | $0.00037 | $0.00799 |
| Sonnet 5.5 | $0.00018 | $0.00399 |
| Haiku 4.5 | $0.00009 | $0.00200 |
Grade A, and why
apply-emergent-scaling 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 4d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Emergent Scaling
When a validated approach is working at its current scale, treat what happens at a much larger scale as a genuinely open, separately testable question rather than assuming proportional or diminishing returns — and separately catalogue the technical, financial, and organizational resistance to scaling so each can be addressed individually, because scale can produce qualitatively new value that cannot be predicted from smaller-scale results.
Why This Is Best Practice
Why best: The specific, checkable claim here is not "bigger is always better" — it's that certain kinds of value are emergent: undetectable and unpredictable from smaller-scale data, appearing only once a scale threshold is actually crossed, rather than smoothly extrapolatable in advance. Because this value genuinely cannot be predicted from below the threshold, the decision to stop scaling once something "works" at a given size is often made without the evidence needed to justify it — the absence of visible further gains in a smaller-scale test says nothing about whether emergent value exists at a larger one. The resistance to actually testing this (technical difficulty, capital requirements, and the organizational instinct to spread resources across many smaller, individually safer bets instead) is real, but is a separate problem from whether scaling would produce value — conflating "scaling is hard" with "scaling wouldn't help" is the specific error this technique targets.
Wei et al., "Emergent Abilities of Large Language Models" (2022): This peer-reviewed research formally documented that certain language-model capabilities do not appear as a smooth function of model scale — they are effectively absent below a certain size and appear only once scale crosses a specific threshold, in a way that could not have been predicted by extrapolating performance curves from smaller models. This provides rigorous, independent, peer-reviewed grounding for the general claim that scale can produce qualitatively new capabilities rather than merely proportionally more of the same capability — a finding distinct from and stronger than an informal observation that "bigger models tend to do better."
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.
- 4d ago First seen · 65 lines · 92 tokens per session scan A f8cb2d96a25f
apply-emergent-scaling is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 92 tokens to every session and 1,997 once invoked, about $0.0004 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-10-17.
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.