loom-builder-complexity

loom-builder-complexity is a skill for Claude Code, Codex from rjwalters/kicad-tools. It costs 34 tokens per session (5,447 once invoked), scanned A, original, MIT.

A builder guide for judging work complexity, breaking large tasks into smaller issues, and managing scope while developing software.

In plain words
What is it for?
Use it when assessing an issue, splitting it into sub-issues, or deciding whether to complete, decompose, or block claimed work.
Why use it?
It helps prevent work from being abandoned or becoming too large to finish by requiring a clear outcome, smaller tasks, or a documented blocker.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./.loom/scripts/create-issue.sh --parent 812 --title "Part 1: Core functionality" --body "..." --label "loom:triage".

Good fit Use it when assessing an issue, splitting it into sub-issues, or deciding whether to complete, decompose, or block claimed work.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/rjwalters/kicad-tools
agentmods
npx agentmods add skills/rjwalters/kicad-tools/loom-builder-complexity

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 loom-builder-complexity

README.md
[![agentmods](https://agentmods.dev/badge/skills/rjwalters/kicad-tools/loom-builder-complexity/github.svg)](https://agentmods.dev/skills/rjwalters/kicad-tools/loom-builder-complexity)
Your own site
<a href="https://agentmods.dev/skills/rjwalters/kicad-tools/loom-builder-complexity"><img src="https://agentmods.dev/badge/skills/rjwalters/kicad-tools/loom-builder-complexity/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 loom-builder-complexity

Your own site · 80×15
<a href="https://agentmods.dev/skills/rjwalters/kicad-tools/loom-builder-complexity"><img src="https://agentmods.dev/badge/skills/rjwalters/kicad-tools/loom-builder-complexity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,447 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.00034 $0.05447
Opus 5.5 $0.00014 $0.02179
Sonnet 5.5 $0.00007 $0.01089
Haiku 4.5 $0.00003 $0.00545

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

Security

Grade A, and why

loom-builder-complexity 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 2d 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.

.agents/skills/loom-builder-complexity/SKILL.md · 560 lines

How it starts

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

Builder: Complexity Assessment and Issue Decomposition

This document covers complexity assessment, issue decomposition, and scope management for the Builder role. For the core builder workflow, see builder.md.

Contents

⚠️ --body @path Does NOT Expand — It Posts the Literal String

If you post a comment via gh issue comment / gh pr comment / gh api ... comments from a scratch file, --body @path (and gh api -f body=@path) posts the literal string @path, not the file's contents. Full pitfall, incident citation, and fixes: comment-body-literal-path.md.

Never Abandon Work

You must NEVER stop work on a claimed issue without creating a clear path forward.

When you claim an issue with loom:building, you are committing to ONE of these outcomes:

  1. Create a PR - Complete the work and submit for review
  2. Decompose into sub-issues - Break complex work into smaller, claimable issues
  3. Mark as blocked - Document the blocker and add loom:blocked label

Read the full file on GitHub · 560 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. 2d ago Changed · -7 lines 4c0b0da4e1da
  2. 4d ago Changed · -1 lines 4355f1ec5981
  3. 5d ago Changed 6d4d761d8235
  4. 10d ago Changed · +1 lines e1ac31cfa855
  5. 12d ago Changed · -7 lines 3bd0f24dd7c0
  6. 13d ago Changed e7c90ecf80fa
  7. 17d ago Changed · -10 lines a393f8f6a646
  8. 23d ago First seen · 584 lines · 34 tokens per session scan A 89adb8d8a01f

Subscribe to this mod's changes

loom-builder-complexity is a skill published in the GitHub repository rjwalters/kicad-tools (70 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 5,447 once invoked, about $0.0001 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-24.

Related

Other skills, from other repositories

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

Donchitos/Claude-Code-Game-Studios · 35 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens

ring:mapping-feature-relationships

Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…

LerianStudio/ring · 104 tokens