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/seasonedcc/discord-manager/framework-foldernpx skills add seasonedcc/discord-manager --skill framework-foldergit clone --depth 1 https://github.com/seasonedcc/discord-managerWrote 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/seasonedcc/discord-manager/framework-folder)<a href="https://agentmods.dev/skills/seasonedcc/discord-manager/framework-folder"><img src="https://agentmods.dev/badge/skills/seasonedcc/discord-manager/framework-folder.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 | $0.00051 | $0.00792 |
| Opus 5 | $0.00026 | $0.00396 |
| Sonnet 5 | $0.00010 | $0.00158 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
framework-folder 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Framework Folder
Everything here documents the repository as it is on main. If main disagrees with this file, main wins: follow it and flag the drift.
app/framework/ contains zero product-specific logic. It stays self-contained enough to be extracted as a separate npm package at any moment — nothing in it may know that this product manages Discord.
What belongs in app/framework/
Only reusable abstractions any app built on this framework would need:
db.server.ts—makeDb, the migration provider,createDbMigration,migrateDbToLatest/migrateDbDown. Connection construction, WAL and foreign-key pragmas, theCamelCasePluginwiring.env.server.ts— themakeTypedEnvironmentfactory and the framework-only env schema. Loadenv-varsfor the two-tier pattern.scheduler.server.ts—makeJob,makeCronJob,makeSchedulerRunner. An in-process scheduler, no queue.globals.ts—getOrSetGlobal, the HMR- and test-safe singleton holder.helpers.ts— pure helpers, added only when a second caller actually needs one.
What does NOT belong in app/framework/
- Product env vars (
DISCORD_BOT_TOKEN,DISCORD_OWNER_USER_ID,DISCORD_GUILD_ID) - Domain models: guilds, channels, messages, bookmarks, digests
discord.js,@modelcontextprotocol/sdk, or any knowledge of the MCP tool shape- Product configuration or copy
- Anything that references
app/business/,app/mcp/,app/ingest/, orapp/db/
A helper that mentions a product noun in its name or its types belongs in app/business/ instead.
Import direction
The dependency flow is strictly one-directional:
app/business/ → imports from → app/framework/
app/mcp/ → imports from → app/framework/
app/ingest/ → imports from → app/framework/
app/db/ → imports from → app/framework/
app/test/ → imports from → app/framework/
app/framework/ → NEVER imports from → app/business/, app/mcp/, app/ingest/, app/db/, or app-level files
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.
- 4d ago First seen · 73 lines · 51 tokens per session scan A c5dcbbb42a75
framework-folder is a skill published in the GitHub repository seasonedcc/discord-manager (3 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 792 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…