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 ihabkhaled/AI-Psychiatry --skill install-frameworkgit clone --depth 1 https://github.com/ihabkhaled/AI-PsychiatryWrote 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/ihabkhaled/ai-psychiatry/install-framework)<a href="https://agentmods.dev/skills/ihabkhaled/ai-psychiatry/install-framework"><img src="https://agentmods.dev/badge/skills/ihabkhaled/ai-psychiatry/install-framework.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.00048 | $0.00622 |
| Opus 5 | $0.00024 | $0.00311 |
| Sonnet 5 | $0.00010 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
install-framework 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 5d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install AI Psychiatry Framework
Apply the framework to the repository currently being worked on.
Canonical specification
Read references/master-prompt.md before implementation. That file is the authoritative installation and maintenance specification.
For the 0.3.0 and 0.4.0 complementary layers, also read only when relevant:
- loophole enhancement prompts for semantic anti-gaming.
- underthinking and reasoning balance for sufficient reasoning.
- relentless execution and all-in-one orchestration for
never-stopandall-the-medicine.
Packaged implementation
The plugin root is two directories above this file. Inspect:
- ../../.ai/manifests/install.json for required install layers.
- ../../.ai/rules/ for focused operational rules.
- ../../.ai/skills/ for target-repository skill adapters.
- ../../.ai/guides/ for substantive interventions and the failure-mode catalog.
- ../../.ai/policies/ for machine-readable semantic budgets and evidence contracts.
- ../../.ai/executive-function/ for state and machine policy.
- ../../scripts/executive_control.py for deterministic observable-state assessment.
Use these as canonical merge sources. Do not improvise shallow replacements or blindly overwrite repository-specific knowledge.
Execution contract
- Inspect the repository's existing AI-agent architecture first.
- Preserve useful repository-specific rules and generated systems.
- Do not create a competing parallel knowledge architecture.
- Establish the smallest coherent canonical source of truth.
- Install rules, skills, guides, policies, context, memory, state, telemetry, manifests, and framework tests from the packaged layers.
- Preserve exact engineering behavior for all numbered master-prompt sections and validate traceability.
- Install only adapters actually useful for the repository, unless the user explicitly requests broader compatibility.
- Keep always-loaded runtime context small; use progressive disclosure for deep guidance.
- Use evidence before repository claims.
- Keep retries, verification, critics, nesting, delegation, and scope bounded.
- Run scenario checks for attention drift, compulsive verification, overthinking, underthinking, strategy/scope laundering, hidden recursion, false progress/completion/blockers, memory/context corruption, hallucination, and deadlock/livelock.
- Validate what changed with the repository's real tooling.
- Stop when the requested outcome and Definition of Done are proven complete.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 58 lines · 48 tokens per session scan A 9bfba9bfdaba
install-framework is a skill published in the GitHub repository ihabkhaled/AI-Psychiatry (3 stars, last pushed 24d ago), licensed MIT. It adds 48 tokens to every session and 622 once invoked, about $0.0002 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
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
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.
setting-up-a-project
Use whenever asked to set up, onboard, initialize, or spec a project — the front door when the workspace has no spec graph yet (brand-new or an existing codebase); also seeded by the app's Set-up-project card (/skill:setting-up-a-project). Not for feature work in an already-specced project — use the brainstorming…
animate
Build a web animation: whether it should animate at all, the purpose, the tool, the properties, the easing curve, the duration, interruption and exit. Writes the CSS or Motion code for dropdowns, modals, toasts, tooltips, accordions, press feedback, stagger and scroll reveals. Use to animate something or make a…
building-agents
Use when building or restructuring an LLM agent — provider adapter, tool calling, structured output, RAG, agent loop, eval gate, cost routing, tracing, MCP server — model-agnostic across OpenAI/Anthropic/Gemini/OSS so a model swap is a config change. NOT vector-store SQL alone (that is postgresdb) or service…
community
Use when building or running a persistent two-way community space — Discord, Telegram, Circle: platform choice, structure, onboarding, native→bot→human moderation, rituals, growth loops, health metrics. NOT churn of paying product customers (that is retention), NOT broadcast email (that is newsletter), NOT one live…