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.
git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/setup-company)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/setup-company"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/setup-company.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.1 | $0.00016 | $0.01555 |
| Opus 5 | $0.00008 | $0.00777 |
| Sonnet 5 | $0.00003 | $0.00311 |
| Haiku 4.5 | $0.00002 | $0.00155 |
Grade A, and why
setup-company 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 4d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap einer neuen Paperclip-Company
Argumente
company-name(erforderlich) — kurzer, beschreibender Name (z.B. "Acme Labs")
MISSION
Führen Sie einen Operator durch das Onboarding: installieren, die Instanz erstellen, das initiale Operator-Konto bootstrappen, die Company via UI erstellen und den ersten Agent mit dem claude-local-Adapter ausführen.
Die echte
paperclipaiCLI (v2026.609.0) exponiert keinencompanies create-Befehl. Company-Erstellung erfolgt entweder über das Dashboard oder durch Import eines Pakets mitpaperclipai company import. Erfinden Sie keine Flags, die nicht existieren — öffnen Siepaperclipai company --helpund folgen Sie dem, was dort steht.
Vorgehensweise
1. Vorbedingungen
- Node.js 20+ und pnpm 9.15+ installiert
- PostgreSQL erreichbar ODER akzeptieren Sie das eingebettete Postgres für Local-Dev
- Port 3100 verfügbar (oder setzen Sie
PORT)
2. Installieren & Onboarden
Schnellster Pfad:
npx paperclipai onboard --yes
Oder aus einem Checkout:
git clone https://github.com/paperclipai/paperclip.git
cd paperclip
pnpm install
pnpm dev
Das Dashboard ist standardmäßig unter http://localhost:3100 (oder welchen PORT Sie auch immer gesetzt haben).
3. Diagnose-Check
paperclipai doctor
# oder, um Auto-Reparaturen zu versuchen:
paperclipai doctor --repair --yes
Beheben Sie alles, was als Hard-Failure gemeldet wird, bevor Sie fortfahren.
4. Bootstrap des ersten Operators (CEO)
Zwei Pfade stehen je nach Deployment-Kontext zur Verfügung:
A — Browser-Claim (private / self-hosted, nicht beanspruchte Instanz): Wenn die Instanz noch nicht beansprucht wurde, navigieren Sie zu http://localhost:3100 im Browser. Ein Erststart-Bildschirm sollte erscheinen, der die direkte Einrichtung des initialen Admin-Kontos ermöglicht. Verwenden Sie diesen Pfad bei einer frisch deployten Instanz ohne bestehenden Operator.
B — CLI-Bootstrap: Führen Sie den CLI-Befehl aus, um das initiale Operator-Konto programmatisch zu erstellen:
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.
- 4d ago First seen · 168 lines · 16 tokens per session scan A 8ce46e7cb82a
setup-company is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 16 tokens to every session and 1,555 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-09-03.
Other commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.
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.