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/apiliumcode/mayros/discordnpx skills add ApiliumCode/mayros --skill discordgit clone --depth 1 https://github.com/ApiliumCode/mayrosWhat 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.00013 | $0.01025 |
| Opus 5 | $0.00006 | $0.00513 |
| Sonnet 5 | $0.00003 | $0.00205 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
discord 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.
This is a copy
97% identical to discord — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discord (Via message)
Use the message tool. No provider-specific discord tool exposed to the agent.
Musts
- Always:
channel: "discord". - Respect gating:
channels.discord.actions.*(some default off:roles,moderation,presence,channels). - Prefer explicit ids:
guildId,channelId,messageId,userId. - Multi-account: optional
accountId.
Guidelines
- Avoid Markdown tables in outbound Discord messages.
- Mention users as
<@USER_ID>. - Prefer Discord components v2 (
components) for rich UI; use legacyembedsonly when you must.
Targets
- Send-like actions:
to: "channel:<id>"orto: "user:<id>". - Message-specific actions:
channelId: "<id>"(orto) +messageId: "<id>".
Common Actions (Examples)
Send message:
{
"action": "send",
"channel": "discord",
"to": "channel:123",
"message": "hello",
"silent": true
}
Send with media:
{
"action": "send",
"channel": "discord",
"to": "channel:123",
"message": "see attachment",
"media": "file:///tmp/example.png"
}
- Optional
silent: trueto suppress Discord notifications.
Send with components v2 (recommended for rich UI):
{
"action": "send",
"channel": "discord",
"to": "channel:123",
"message": "Status update",
"components": "[Carbon v2 components]"
}
componentsexpects Carbon component instances (Container, TextDisplay, etc.) from JS/TS integrations.- Do not combine
componentswithembeds(Discord rejects v2 + embeds).
Legacy embeds (not recommended):
{
"action": "send",
"channel": "discord",
"to": "channel:123",
"message": "Status update",
"embeds": [{ "title": "Legacy", "description": "Embeds are legacy." }]
}
embedsare ignored when components v2 are present.
React:
{
"action": "react",
"channel": "discord",
"channelId": "123",
"messageId": "456",
"emoji": "✅"
}
Read:
{
"action": "read",
"channel": "discord",
"to": "channel:123",
"limit": 20
}
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 · 198 lines · 13 tokens per session scan A 69fe0bc1e69c
discord is a skill published in the GitHub repository ApiliumCode/mayros (12 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,025 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to discord, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
campaign
Start, drive, monitor, and stop an Autonomous Improvement Campaign — a durable, repeatable wrapper around the dev-improve loop.
dev-loop
Pull the next task from a platform Ralph Loop queue (via the devloop MCP bridge) and drive it to a verified, committed, reported outcome. One task per invocation — this is a Ralph-pattern loop body designed to be driven repeatedly by /loop /dev-loop.
improve
Discover, offer, and triage code-quality improvements for the dev-improve loop.
gen-tests
Generate RSpec request specs for untested controllers and service specs for untested services.
verify
Run targeted verification based on what changed since last commit.
audit
Run comprehensive codebase quality and pattern compliance audit.