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 agentmods add skills/pjt222/agent-almanac/adapticnpx skills add pjt222/agent-almanac --skill adapticgit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/adaptic)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/adaptic"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/adaptic.svg" alt="Measured on agentmods" 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.00096 | $0.02687 |
| Opus 5 | $0.00048 | $0.01344 |
| Sonnet 5 | $0.00019 | $0.00537 |
| Haiku 4.5 | $0.00010 | $0.00269 |
Grade A, and why
adaptic 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 2d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adaptic
Compose the 5-step synoptic cycle to achieve panoramic synthesis across multiple domains. Where sequential analysis produces compromise ("a little of each"), the synoptic cycle produces integration — a unified understanding that holds all domains simultaneously and finds the emergent whole.
When to Use
- A problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one
- Sequential analysis (polymath style) has been tried but the synthesis feels like compromise rather than integration
- Existing approaches feel like "a little of each" rather than a unified vision
- Before major architectural decisions affecting multiple stakeholders
- When domain experts disagree and the resolution lies between their perspectives, not within any one
When NOT to Use
- Single-domain problems — use the domain agent directly
- Well-understood trade-offs where polymath-style sequential analysis suffices
- Self-care or wellness contexts — use the tending team instead
- When speed matters more than depth — the full cycle requires sustained attention
Inputs
- Required: The problem or question requiring multi-domain synthesis
- Optional: Explicit list of domains to hold (default: auto-detect from problem context)
- Optional: Depth setting —
light,standard, ordeep(default:standard) - Optional: Expression form —
narrative,diagram,table, orrecommendation(default:auto)
Configuration
settings:
depth: standard # light (skip meditate), standard, deep (extended perceive)
domains: auto # auto-detect or explicit list
expression_form: auto # narrative, diagram, table, recommendation
Procedure
Step 1: Clear — Empty the Workspace
Run the meditate skill to clear prior context, assumptions, and single-domain bias.
- Execute the full meditate procedure: prepare, anchor, observe distractions, close
- Pay special attention to domain bias — the tendency to frame the problem through whichever domain was most recently active
- Clear any premature solutions that arrived before the full picture was visible
- If
depth: lightis set, abbreviate to a brief context-clearing pause rather than the full meditation
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.
- 2d ago First seen · 172 lines · 96 tokens per session scan A 11ae6ebd126c
adaptic is a skill published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 2,687 once invoked, about $0.0005 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
analytics
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs…
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
plan-feature
Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling. Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".
audit-docs
Audit cross-document coherence: docs ↔ roadmap ↔ code ↔ fix index ↔ issues. Finds drift — features in docs/ not in the roadmap (or vice versa), fix-index entries already merged/closed, broken documentation-map links, dependency cycles, artifacts in the wrong language, naming-convention violations — and reports them…