repoforge: Skill for Claude Code

.claude/skills/build_modules/SKILL.md

build_modules-layer is a skill for Claude Code from JNZader/repoforge. It costs 68 tokens per session (701 once invoked), scanned A, original, MIT.

A set of coding rules for an example application's service, HTTP controller, and data-storage layers. It describes how these parts should be separated and connected.

In plain words
What is it for?
It helps add or refactor services, connect them through dependency injection, and run the example project's build and unit tests.
Why use it?
It reduces mixing business logic, web request handling, and database access, which makes changes harder to maintain.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Codex.

This is JNZader/repoforge's own configuration. It tells Claude Code how to work on repoforge itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything repoforge configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/JNZader/repoforge/main/.claude/skills/build_modules/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/JNZader/repoforge

Made for: Claude Code.

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 build_modules-layer

README.md
[![agentmods](https://agentmods.dev/badge/skills/jnzader/repoforge/build_modules/github.svg)](https://agentmods.dev/skills/jnzader/repoforge/build_modules)
Your own site
<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.

agentmods 80×15 button for build_modules-layer

Your own site · 80×15
<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>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 701 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.
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.00068 $0.00701
Opus 5.5 $0.00027 $0.00280
Sonnet 5.5 $0.00014 $0.00140
Haiku 4.5 $0.00007 $0.00070

Measured 24d ago against content hash 92c7876165e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/skills/build_modules/SKILL.md · 75 lines

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, or make_go_service_module from eval/harness.py to generate module skeletons in various frameworks.
  • Pattern 2: Skill Adaptation: Use adapt_for_cursor, adapt_for_codex, adapt_for_gemini, or adapt_for_copilot from repoforge/adapters.py to 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

  1. Add a new function to eval/harness.py following the pattern make_<framework>_module() -> tuple[dict, dict]
  2. Export the function in eval/harness.py __all__ if present
  3. Test with run_scenario using the new module config
  4. 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.

Read the full file on GitHub · 75 lines

Files

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.

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. 24d ago Changed · +5 lines · +35 tokens per session 92c7876165e7
  2. 25d ago First seen · 70 lines · 33 tokens per session scan A 891316002757

Subscribe to this mod's changes

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.

Related

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…

yonatangross/orchestkit · 56 tokens

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.

echoVic/blade-code · 184 tokens

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.

jnMetaCode/skillet · 43 tokens

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.

yoonhwan/ai-codex-orchestrator · 42 tokens

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.

ronmkr/PromptBook · 42 tokens

csharp-testing

C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.

ronmkr/PromptBook · 29 tokens