Borrowing it
Nothing to install: this file belongs to JNZader/repoforge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JNZader/repoforge/main/.claude/skills/build_modules/SKILL.mdgit clone --depth 1 https://github.com/JNZader/repoforgeWrote 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/jnzader/repoforge/build_modules)<a href="https://agentmods.dev/skills/jnzader/repoforge/build_modules"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/build_modules/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/jnzader/repoforge/build_modules"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/build_modules.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.00068 | $0.00701 |
| Opus 5.5 | $0.00027 | $0.00280 |
| Sonnet 5.5 | $0.00014 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
build_modules-layer 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 24d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
build_modules-layer
This layer provides tools for building, evaluating, and analyzing Python modules within the Gentleman-Skills ecosystem. It handles module generation, LLM target adaptation, and code quality analysis.
Trigger: When working in build_modules/ directory — adding, modifying, or debugging module generation, adaptation, or analysis.
Quick Reference
| Task | Pattern |
|---|---|
| Run eval scenarios | python -m eval.harness run_all |
| Adapt skills for LLM targets | adapt_for_cursor/Codex/Gemini/Copilot |
| Detect dead code | detect_dead_code() |
Critical Patterns (Summary)
- Pattern 1: Module Generation: Use
make_fastapi_crud_module,make_nextjs_page_module,make_mixed_layer, ormake_go_service_modulefromeval/harness.pyto generate module skeletons in various frameworks. - Pattern 2: Skill Adaptation: Use
adapt_for_cursor,adapt_for_codex,adapt_for_gemini, oradapt_for_copilotfromrepoforge/adapters.pyto transform skill dictionaries for specific LLM targets.
When to Use
- Adding a new module generation function to
eval/harness.py - Adapting existing skills for a different LLM target platform
- Detecting dead code or analyzing module complexity
- Running eval scenarios against generated modules
Adding a New Module Generation Function
- Add a new function to
eval/harness.pyfollowing the patternmake_<framework>_module() -> tuple[dict, dict] - Export the function in
eval/harness.py__all__if present - Test with
run_scenariousing the new module config - Verify output with
print_report
Commands
python -m eval.harness run_all
python -m eval.harness run_scenario <scenario_name>
adapt_for_cursor <skills_json>
adapt_for_copilot <skills_json>
detect_dead_code <ast_symbols_dict>
Anti-Patterns
Don't: Mix adaptation targets — using adapt_for_copilot skills with adapt_for_cursor expectations — each adapter formats skill dicts differently for its target LLM, causing integration failures.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 24d ago Changed · +5 lines · +35 tokens per session 92c7876165e7
- 25d ago First seen · 70 lines · 33 tokens per session scan A 891316002757
build_modules-layer is a skill published in the GitHub repository JNZader/repoforge (5 stars, last pushed 24d ago), licensed MIT. It adds 68 tokens to every session and 701 once invoked, about $0.0003 per session on Opus 5.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-27.
Other skills, from other repositories
architecture-patterns
Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right…
knowledge-engineering-quality-and-delivery-unit-integration-and-shared-test-harnesses
A testing guide for the CLI and web interfaces, covering unit, integration, end-to-end, and real-process test setup with shared fixtures and cleanup.
test-writing
Write tests that catch real regressions — behavior-focused, minimal mocking, edge cases chosen from the code's actual branches. Use when adding tests for new code or backfilling tests for a fix.
aco-backend-coder
A backend development guide focused on APIs, business rules, login and access control, middleware, and basic unit tests. Stripe is a payment-services company, so the description uses its engineering standards as a reference point.
ai-regression-testing
Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.
csharp-testing
C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.