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 event4u-app/agent-config --skill module-managementgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/module-management)<a href="https://agentmods.dev/skills/event4u-app/agent-config/module-management"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/module-management/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/event4u-app/agent-config/module-management"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/module-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01933 |
| Opus 5 | $0.00023 | $0.00966 |
| Sonnet 5 | $0.00009 | $0.00387 |
| Haiku 4.5 | $0.00005 | $0.00193 |
Grade A, and why
module-management 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 8d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
module
When to use
Use this skill when creating, exploring, or working within a module under
any directory listed in modules.root_paths (team setting in
.agent-project-settings.yml). The skill is stack-agnostic — Laravel
HMVC, Symfony DDD-lite, Node monorepo, Python src layout, Go internal/,
or a custom path all flow through the same procedure with a
stack-specific carve-out at the bottom.
When modules.enabled is false (the default) the skill is a no-op —
the project does not opt into module-aware behavior.
Understand the current layout before editing
Before creating, renaming, or modifying anything inside a module:
- Read the
modules:block from.agent-project-settings.yml— never assume a specific module root. - List the existing modules under each
modules.root_pathsentry and review the target module'sREADME.md(orpackage.json/pyproject.tomldescription) to understand its purpose. - Read any module-scoped agent docs under
{module_root}/{ModuleName}/{modules.agent_folder}/contexts/. - Match the stack carve-out below by
modules.namespace_templateshape and confirm the conventions before generating files.
Skip this step → risk creating files in the wrong root, breaking stack-native auto-loading, or duplicating existing modules.
Procedure: Work with modules
- Read
modules:block from.agent-project-settings.ymlvia the loader (get_modules_config()inscripts/_lib/agent_settings.ts). - For each path in
modules.root_paths, read the module'sREADME.md(orpackage.json/pyproject.tomldescription) for purpose. - If module-level agent docs exist under
{module_root}/{modules.agent_folder}/(defaultagents/), read them. - Match the stack carve-out below by
modules.namespace_templateshape or root-path heuristic — apply stack-specific conventions on top of the generic procedure.
Detection (fallback when modules: block is empty)
When modules.enabled is unset / false, the skill consults the
auto-detection table in
/module explore Step 1 — same six
stack shapes, fallback only. The skill never writes the modules:
block automatically; that is propose_modules_config.ts plus user
confirmation per
/agents init Step 7.
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.
- 8d ago First seen · 233 lines · 47 tokens per session scan A 3d6f0fc201f2
module-management is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 1,933 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-04.
Other skills, from other repositories
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
pad
Talk to your project. Natural-language project management — create items, check status, plan work, brainstorm ideas, and more.
pm-arch
Skill "pm-arch" from wei63w/pm-manager, covering user input, outline, done when and shared workflow (all /pm- commands).
pm-discover
Skill "pm-discover" from wei63w/pm-manager, covering user input, outline and shared workflow.