module-detect-on-the-fly

module-detect-on-the-fly is a skill for Claude Code, Codex from event4u-app/agent-config. It costs 52 tokens per session (2,181 once invoked), scanned A, original, MIT.

A detection guide for recognizing module-shaped folders such as packages, apps, or internal components when module settings are not enabled.

In plain words
What is it for?
Use it when working in a likely module directory to check project settings, detect module roots, and offer to enable module-aware behavior.
Why use it?
It prevents the agent from overlooking a modular project structure or applying module rules without first asking whether the project should enable them.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

Good fit Use it when working in a likely module directory to check project settings, detect module roots, and offer to enable module-aware behavior.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/event4u-app/agent-config/module-detect-on-the-fly
Install

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.

Any agent
npx skills add event4u-app/agent-config --skill module-detect-on-the-fly
Clone the repo
git clone --depth 1 https://github.com/event4u-app/agent-config

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for module-detect-on-the-fly

README.md
[![agentmods](https://agentmods.dev/badge/skills/event4u-app/agent-config/module-detect-on-the-fly/github.svg)](https://agentmods.dev/skills/event4u-app/agent-config/module-detect-on-the-fly)
Your own site
<a href="https://agentmods.dev/skills/event4u-app/agent-config/module-detect-on-the-fly"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/module-detect-on-the-fly/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.

agentmods 80×15 button for module-detect-on-the-fly

Your own site · 80×15
<a href="https://agentmods.dev/skills/event4u-app/agent-config/module-detect-on-the-fly"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/module-detect-on-the-fly.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,181 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.02181
Opus 5 $0.00026 $0.01091
Sonnet 5 $0.00010 $0.00436
Haiku 4.5 $0.00005 $0.00218

Measured 8d ago against content hash ea561ebca2b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

module-detect-on-the-fly 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.

src/skills/module-detect-on-the-fly/SKILL.md · 188 lines

How it starts

The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.

module-detect-on-the-fly

When to use

Fires the first time the agent edits, reads, or references a file inside a module-shaped path while the project has not yet opted into the module config. Goal: catch projects with real module structure that never ran /agents init or the GUI wizard, and offer to enable the config — once, without nagging.

Trigger heuristic (any one):

  • The agent is about to edit a path matching */Modules/*, */app/Modules/*, */packages/*/<non-noise>, */apps/*/<non-noise>, */src/Module*/*, or */internal/*/<non-noise>.
  • The user names such a path in their request.
  • A /module * command runs while modules.enabled is false.

Hard gate — skip the skill entirely when any of these hold:

  1. modules.enabled is true (already configured — use module-management).
  2. modules.detection_acknowledged is true (user already answered).
  3. The path matches a _NOISE_SEGMENTS entry (vendor, node_modules, dist, build, etc.) — see scripts/_lib/module_detection.ts.

Confirm both flags via get_modules_config() before running detection.

Procedure

  1. Detect — call detect_module_roots(project_root) from scripts/_lib/module_detection.ts. Returns a list of ModuleCandidate ordered high → medium confidence.

  2. Bail early — if the list is empty OR every candidate has confidence: "medium" AND no candidate matches the path the agent is currently working on, skip silently. (False positives nag worse than missed detections.)

  3. Surface once — present a single numbered-options block:

    Detected module-shaped structure not yet in config:
    - app/Modules/  (laravel-hmvc, high confidence, 4 modules)
    - packages/     (node-monorepo, medium confidence, 2 candidates)
    
    1. Enable modules config — add detected paths to
       `.agent-project-settings.yml` so module-aware skills activate.
    2. Not now — silence this prompt for the project (you can revisit
       via `/agents init` later).
    3. Show details first — list the candidates with their stack guess
       and per-module subdirs before deciding.
    
    Recommendation: 1 when the high-confidence list matches your
    intent. 2 when the layout is intentionally flat.
    

Read the full file on GitHub · 188 lines

Changes

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.

  1. 8d ago First seen · 188 lines · 52 tokens per session scan A ea561ebca2b6

Subscribe to this mod's changes

module-detect-on-the-fly is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 2,181 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-09-04.