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/khanh-vu/claude-force/restructuregit clone --depth 1 https://github.com/khanh-vu/claude-forceWrote 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/commands/khanh-vu/claude-force/restructure)<a href="https://agentmods.dev/commands/khanh-vu/claude-force/restructure"><img src="https://agentmods.dev/badge/commands/khanh-vu/claude-force/restructure.svg" alt="Measured on agentmods" 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 | $0.00008 | $0.01929 |
| Opus 5 | $0.00004 | $0.00964 |
| Sonnet 5 | $0.00002 | $0.00386 |
| Haiku 4.5 | $0.00001 | $0.00193 |
Grade A, and why
restructure 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 3d 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Restructure Command
Validate and fix existing .claude folder structure to ensure claude-force compatibility.
Purpose
The /restructure command helps you:
- Validate existing .claude folder structure
- Detect missing required files and directories
- Fix invalid claude.json configuration
- Create missing files with proper templates
- Ensure project is ready for claude-force
Usage
Basic Restructure (Current Directory)
/restructure
Restructure Specific Directory
/restructure /path/to/project
With Auto-Approve (No Prompts)
/restructure --auto
Interactive Mode (Review Each Fix)
/restructure --interactive
What Gets Validated
Required Files
README.md- Project overviewclaude.json- Configuration filetask.md- Task specificationscorecard.md- Quality checklist
Required Directories
agents/- Agent definitionscontracts/- Agent contractshooks/- Governance hooksmacros/- Reusable instruction blockstasks/- Task context tracking
Optional Files (Warnings)
work.md- Agent output workspacecommands.md- Common commands referenceworkflows.md- Multi-agent workflow patterns
Configuration Validation
- claude.json structure:
- Required fields: version, name, agents, workflows, governance, paths, rules
- Valid JSON syntax
- Agent file references exist
- Contract file references exist
Implementation
You should execute this command by:
- Import the RestructureCommand class:
from claude_force.commands.restructure import RestructureCommand
from pathlib import Path
-
Determine the project path:
- If user provides a path argument, use that
- Otherwise, use current working directory
- Validate the path exists and is a directory
-
Execute the restructure:
# Create command instance
command = RestructureCommand(Path(project_path))
# Auto mode - apply all fixes without prompting
result = command.execute(auto_approve=True)
# Interactive mode - ask user for each fix
result = command.execute(auto_approve=False)
# Format output
output = command.format_markdown(result)
print(output)
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.
- 3d ago First seen · 364 lines · 8 tokens per session scan A c8d3749e416f
restructure is a command published in the GitHub repository khanh-vu/claude-force (5 stars, last pushed 9mo ago), licensed MIT. It adds 8 tokens to every session and 1,929 once invoked, about $0.0000 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.