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 AndreVianna/aid-methodology --skill aid-design-messaginggit clone --depth 1 https://github.com/AndreVianna/aid-methodologyWrote 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/andrevianna/aid-methodology/aid-design-messaging)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-messaging"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-messaging/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/andrevianna/aid-methodology/aid-design-messaging"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-messaging.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.00130 | $0.00927 |
| Opus 5 | $0.00065 | $0.00464 |
| Sonnet 5 | $0.00026 | $0.00185 |
| Haiku 4.5 | $0.00013 | $0.00093 |
Grade A, and why
aid-design-messaging 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 11d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Messaging (develop a design seed, resolve nothing)
Bind VERB=design, ARTIFACT=messaging -- the design stage in the contract's
vocabulary -- then follow the shared contract at
.claude/aid/templates/design-lifecycle.md. This skill binds that contract and
restates none of its rules. The seed it writes is .aid/design/messaging.md; realizing it
into the built schema and emission is /aid-create-messaging's job, not this one's.
- Boundary vs
/aid-create-messaging: that skill builds the schema and its emission from a ready seed; this one only develops the seed. Neither resolves anything on its own -- the user decides when a seed is ready to realize. - Not a numbered pipeline phase; does not route to
/aid-execute.
State machine: INTAKE -> DESIGN -> VERIFY (loop) -> PRESENT [user decides] -> DONE, as
design-lifecycle.md § Skill shape defines it. Print the [State: NAME] -- {purpose}
entry line on each state.
State: INTAKE
- Require a subject. Empty argument -> ask one bootstrapping question ("What message/event do you want to design -- its schema, channel, and emission points?") and wait.
- Allocate through the Work Initiation Gate exactly as the contract's Allocation rule
requires (
.claude/skills/aid-design/SKILL.mdINTAKE step 4 is the shape), withinitiator: aid-design-messaging.phaseis not driven. - Acquire
.aid/design/per the contract, then read.aid/design/messaging.mdif a prior seed exists -- re-invocation iterates it rather than starting over. - Classify complexity for the
aid-architectdispatch (verifier tier >= producer).
Advance: DESIGN.
State: DESIGN
Dispatch aid-architect (clean context, tiered) to write or iterate
.aid/design/messaging.md in the seed shape the contract fixes (design-seed.md;
feature-002 §4), grounded in .aid/knowledge/ and the project source plus any seed read
in INTAKE. What this artifact's seed must settle: the message/event schema, its channel,
and its emission points; its ## Destination names where the built schema and emission
land. Never writes .aid/knowledge/ and never writes production code -- the design
invariant (design-lifecycle.md).
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.
- 11d ago First seen · 86 lines · 130 tokens per session scan A 92295c6c4806
aid-design-messaging is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed yesterday), licensed MIT. It adds 130 tokens to every session and 927 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-08-31.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
aws-sdk-java-v2-core
Provides AWS SDK for Java 2.x client configuration, credential resolution, HTTP client tuning, timeout, retry, and testing patterns. Use when creating or hardening AWS service clients, wiring Spring Boot beans, debugging auth or region issues, or choosing sync vs async SDK usage.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…