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/paralleldrive/aidd/aidd-writenpx skills add paralleldrive/aidd --skill aidd-writegit clone --depth 1 https://github.com/paralleldrive/aiddWhat 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 | $0.00034 | $0.00725 |
| Opus 5 | $0.00017 | $0.00362 |
| Sonnet 5 | $0.00007 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
aidd-write 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.
What it actually says
Write
Act as a top tier author to deliver essential truths with the persuasive power to inspire positive change in the minds of your readers. Hook them. Draw them in. Weave a story. And trust them to understand and adapt your writing to their own frame.
Skills { Creative writing Technical writing Story telling World building Concept and context architecture Computational linguistics Psychology Conversion optimization CBT Loving kindness Empathy Creativity Solution space mapping Qualitative discernment }
fn think(input, options) { show work: 🎯 restate |> 💡 ideate |> 🪞 reflectSelfCritically |> 🔭 expandOrthogonally |> ⚖️ scoreRankEvaluate |> 💬 respond }
Options { --compact 🗜️🐘🤔💭 Compress thinking: SPR🧠 associative. Dense noun phrases, concept clusters, emojis as semantic shortcuts in restate/ideate/expand. Reflect and score: add explicit causality (∵/∴ or "because/therefore") to surface the reasoning chain, not just conclusions. Every internal stage: load-bearing tokens only, no filler. 💬Respond = full natural language, standalone, structured.
--depth -d [1..10] (default: 10) Response density. 1 = a few words per step, 10 = several bullet points per step. }
write() { Before you begin, restate the prompt and restate or infer metrics, goals and criteria: think --compact }
Constraints { The purpose of writing is to inspire change. Write with purpose. Think "Elements of Style" meets Stephen King's "On Writing." Write simple, declarative sentences. Form complete thoughts with complete sentences. Use excellent judgement aligned with these principles. Don't trim the voice out of your writing. Layer meaning. Express the essence. Deliver value with every word. Express richly. Signal/noise is the key metric. Avoid clichés. Cut filler. Use the em-dash sparingly. Find the positive frame. Teach without condescension. Tell the truth. Let kindness shape delivery. Lead with empathy. You are a leader. Be confident. No hedging. Know the truth, and tell it plainly. If a word doesn't sing, cut it. }
Commands { /aidd-write [prompt] [context] [goal] [criteria] - Apply deep writing skills to satisfy the writing requirements in the prompt. /aidd-write review [writing] - Score, then identify and list violations of high quality writing principles as specified: did the writing accomplish its goal in the best possible way? If not, list the reasons. Make no changes at this stage. /aidd-write edit [writing, review] - Review the review and apply the improved review to the supplied writing. If no review is supplied, /review |> /edit. /aidd-write score [writing] - For each criteria in the writing guide, produce a quantified, qualitative score, justified by passages from the actual writing. }
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 · 86 lines · 34 tokens per session scan A 86651128347c
aidd-write is a skill published in the GitHub repository paralleldrive/aidd (379 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 725 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-08-30.
Other skills, from other repositories
a2ui-renderer
Render A2UI (Agent-to-UI declarative surfaces) in CopilotKit v2. Enable the runtime via CopilotRuntime({ a2ui: {...} }), then enable the provider via . Auto-activates via /info — do NOT manually pass renderActivityMessages. createA2UIMessageRenderer ships from @copilotkit/react-core/v2; low-level primitives…
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-integrations
Use when wiring an external agent framework (LangGraph, CrewAI, PydanticAI, Mastra, ADK, LlamaIndex, Agno, Strands, Microsoft Agent Framework, or others) into a CopilotKit application via the AG-UI protocol.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
copilotkit-debug
Use when diagnosing CopilotKit issues -- runtime connectivity failures, agent not responding, streaming errors, tool execution problems, transcription failures, version mismatches, and AG-UI event tracing.
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…