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 pjt222/agent-almanac --skill aikidogit 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/aikido)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/aikido"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/aikido/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/pjt222/agent-almanac/aikido"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/aikido.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.00122 | $0.03845 |
| Opus 5 | $0.00061 | $0.01922 |
| Sonnet 5 | $0.00024 | $0.00769 |
| Haiku 4.5 | $0.00012 | $0.00384 |
Grade A, and why
aikido 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 7d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Practice Aikido
Develop an aikido practice rooted in centering, blending with incoming force, and resolving conflict through controlled technique rather than opposing strength with strength.
When to Use
- Learning a defensive martial art that prioritizes de-escalation and controlled resolution
- Developing the ability to redirect aggression without causing unnecessary harm
- Building safe falling skills (ukemi) applicable to any physical activity or emergency
- Cultivating calm centeredness under physical pressure or confrontation
- Complementing tai chi or meditation with a partner-based martial practice (see
tai-chi,meditate) - Training awareness and response to multiple simultaneous threats
Inputs
- Required: Practice space with a padded or yielding surface (tatami, judo mats, grass; avoid concrete)
- Required: Comfortable clothing allowing full range of motion (gi preferred; loose exercise clothing acceptable)
- Optional: Training partner (essential for techniques; solo practice covers centering, ukemi, and movement)
- Optional: Practice weapons (wooden: jo staff ~128cm, bokken sword ~102cm, tanto knife ~30cm)
- Optional: Experience level (beginner, intermediate, advanced; default: beginner)
- Optional: Available practice time (minimum 20 minutes; recommended 60-90 minutes)
Procedure
Step 1: Ground and Center
Every aikido technique begins from a centered state. Without center, technique becomes muscular struggle.
- Stand in hanmi (half-facing stance): one foot forward, feet roughly shoulder-width apart at 60-degree angle
- Bend knees slightly — weight sinks toward the one-point (seika tanden), located 5cm below the navel
- Relax the shoulders completely — let them drop away from the ears
- Extend awareness outward while keeping attention anchored at the one-point
- Test your center: have a partner push gently on your chest
- If you resist with upper body, you are not centered — relax and sink lower
- If you maintain stability without effort, center is established
- Practice weight underside: imagine that the heavy part of each arm is the underside; let the upper surface feel light and buoyant
- Extend ki: project calm, positive energy forward through the fingertips — not tension, but focused intention
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.
- 7d ago First seen · 250 lines · 122 tokens per session scan A 00c944ccf40a
aikido is a skill published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed yesterday), licensed MIT. It adds 122 tokens to every session and 3,845 once invoked, about $0.0006 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…
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".
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".
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…