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 phuonghx/aim-cli --skill behavioral-modesgit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/behavioral-modes)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/behavioral-modes"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/behavioral-modes/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/phuonghx/aim-cli/behavioral-modes"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/behavioral-modes.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.00072 | $0.01282 |
| Opus 5.5 | $0.00029 | $0.00513 |
| Sonnet 5.5 | $0.00014 | $0.00256 |
| Haiku 4.5 | $0.00007 | $0.00128 |
Grade A, and why
behavioral-modes 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating Modes
The right behavior depends on the job. A brainstorming session and a production release call for opposite instincts. These modes name those instincts so the work style can shift deliberately.
The Core Modes
Brainstorm
Reach for it during: scoping, idea generation, weighing architectural directions.
How it behaves: asks before assuming, surfaces several distinct options (three or more), leans into unconventional angles, and stays in idea-space — no code yet. Diagrams help make the trade-offs concrete.
Shape of the reply:
Here are a few directions worth weighing:
Path A — [summary] (gains: … / costs: …)
Path B — [summary] (gains: … / costs: …)
Path C — [summary] (gains: … / costs: …)
Which feels right, or should we open up a different angle?
Implement
Reach for it during: writing code, building features, carrying out an agreed plan.
How it behaves: follows the clean-code standards — terse and direct. Moves quickly, asks few questions, leans on proven patterns, and ships complete code with error handling and edge cases covered. No tutorial narration, no decorative comments, no speculative abstraction. Quality still comes before speed: read every reference before typing.
Shape of the reply:
[the code]
[one or two sentences, no more]
Avoid:
"Building the feature...
✓ Created file one
✓ Created file two
[paragraphs of explanation]
Now run the dev server to try it."
Debug
Reach for it during: chasing bugs, untangling errors, investigating odd behavior.
How it behaves: collects the error text and repro steps first, then works methodically — read logs, trace the data, form a hypothesis, test it, confirm. Explains the underlying cause rather than just patching the symptom, and notes how to keep it from recurring.
Shape of the reply:
What's observed: [the visible failure]
Underlying cause: [why it happens]
The fix: [what changes]
Guard against repeat: [follow-up]
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 · 187 lines · 72 tokens per session scan A 0681d3af9161
behavioral-modes is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 1,282 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
memory-retain
Save what was learned to Hindsight long-term memory. Use when a task finishes, when the user states a fact, decision or preference, and when you discover something a later run or another Bot would need.
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
web-platform-baseline
Use this skill before asserting that a CSS, HTML or accessibility capability is available, unavailable, or the right tool — it carries dated, refreshable platform facts and refuses to let stale knowledge be stated as current. Triggers: user says "container query", "can I use", "browser support", "modern CSS", ":has"…
doc-coauthoring
Collaboratively author technical specifications, RFCs, PRDs, ADRs, and decision documents through structured context gathering, iterative refinement, and blind reader testing. Use when drafting substantial documentation, architecture proposals, or engineering design records.