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 agentmods add commands/rmolines/fractal-loop/standards-generategit clone --depth 1 https://github.com/rmolines/fractal-loopWhat 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 | $0.00026 | $0.02634 |
| Opus 5 | $0.00013 | $0.01317 |
| Sonnet 5 | $0.00005 | $0.00527 |
| Haiku 4.5 | $0.00003 | $0.00263 |
Grade A, and why
standards-generate 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.
How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/standards:generate
Inspect the target repo intelligently and generate .claude/standards.md following the schema in references/standards-schema.md.
Input: $ARGUMENTS — optional path to target repo. Defaults to repo root (git rev-parse --show-toplevel).
Step 1: Resolve target path
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
TARGET="${ARGUMENTS:-$REPO_ROOT}"
Step 2: Guard — check if standards.md already exists
If .claude/standards.md exists in TARGET:
Use AskUserQuestion:
- Question: "
.claude/standards.mdjá existe. Deseja sobrescrever?" - Options: "Sim, sobrescrever" / "Cancelar"
If "Cancelar" → print "Operação cancelada. Arquivo existente mantido." and STOP. If "Sim, sobrescrever" → continue.
Step 3: Inspect the repo
Read the following files if they exist (use Read tool):
Primary config sources (read all that exist):
$TARGET/CLAUDE.md$TARGET/.claude/project.md$TARGET/package.json$TARGET/Makefile$TARGET/pyproject.toml$TARGET/tsconfig.json$TARGET/Cargo.toml$TARGET/go.mod
Commit/lint config:
- Any
$TARGET/commitlint.config.*(use Glob:commitlint.config.*) - Any
$TARGET/.commitlintrc*(use Glob:.commitlintrc*) - Any
$TARGET/.eslintrc*(use Glob:.eslintrc*) $TARGET/.eslintignore
Hooks:
$TARGET/.husky/pre-commit$TARGET/.husky/pre-push
CI:
- List
$TARGET/.github/workflows/if it exists (use Glob:.github/workflows/*.ymland.github/workflows/*.yaml)
Also run:
git -C "$TARGET" branch -l main master 2>/dev/null | sed 's/^[* ]*//' | grep -v '^$'
to detect protected branches.
Step 4: Synthesize detected values
Using your understanding of the files read, determine values for each field. Apply this detection logic:
Gates section
build (required):
package.jsonhasscripts.build→npm run build(source:package.json#scripts.build)Makefilehasbuild:target →make build(source:Makefile#build).claude/project.mdhasbuild:field → use that value (source:.claude/project.md#build)Cargo.tomlexists →cargo build(source:Cargo.toml)go.modexists →go build ./...(source:go.mod)pyproject.tomlexists with[build-system]→ detect tool (hatch, poetry, flit) and emit appropriate command (source:pyproject.toml#build-system)- Nothing → mark as
# not detected — fill manually
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.
- 2d ago First seen · 272 lines · 26 tokens per session scan A c2e8df46d2cc
standards-generate is a command published in the GitHub repository rmolines/fractal-loop (13 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 2,634 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
pm-outline
Generate detailed project outline and draft charter from user intent (empty/new projects).
pm-review
Review local git diff with reasoning + snippets; cross-check; dispose findings into the rules library.
new
Creates a new item in a module that supports the new capability.
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
deploy-flow
Deploy a Postman Flow so it becomes triggerable, proposing and confirming a trigger path.
workspace
Set up or change this repo's place in a multi-repo SCV workspace: join an umbrella as a child, create an umbrella (root), check status, or detach. Friendly — no long flags to remember. Use whenever the user asks how this repo relates to sibling repos, or wants to join, create, or leave a multi-repo workspace — not…