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 skills add amanning3390/hermeshub --skill paperclipgit clone --depth 1 https://github.com/amanning3390/hermeshubWrote 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/skills/amanning3390/hermeshub/paperclip)<a href="https://agentmods.dev/skills/amanning3390/hermeshub/paperclip"><img src="https://agentmods.dev/badge/skills/amanning3390/hermeshub/paperclip/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.
<a href="https://agentmods.dev/skills/amanning3390/hermeshub/paperclip"><img src="https://agentmods.dev/badge/skills/amanning3390/hermeshub/paperclip.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.01195 |
| Opus 5.5 | $0.00022 | $0.00478 |
| Sonnet 5.5 | $0.00011 | $0.00239 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
paperclip 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 1mo 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paperclip
Open-source orchestration for zero-human companies. If OpenClaw is an employee, Paperclip is the company.
When to Use
- Orchestrating multiple AI agents toward a shared business goal
- Running autonomous agent teams with org charts, budgets, and governance
- Managing agent assignments, delegation, and status tracking via heartbeats
- Setting up cost controls and audit trails for multi-agent workflows
- Coordinating OpenClaw, Claude Code, Codex, Cursor, or any heartbeat-capable agent
How It Works
Paperclip is a Node.js server and React UI that acts as a control plane for AI agent teams:
- Define the goal — "Build the #1 AI note-taking app to $1M MRR."
- Hire the team — CEO, CTO, engineers, designers, marketers — any bot, any provider.
- Approve and run — Review strategy. Set budgets. Hit go. Monitor from the dashboard.
Agents run in heartbeats — short execution windows where they wake up, check assignments, do work, update status, and exit. Delegation flows up and down the org chart.
Architecture
┌─────────────────────────────────────┐
│ Paperclip Server │
│ (Node.js + Postgres + React UI) │
├─────────────────────────────────────┤
│ Org Chart │ Goals │ Budgets │ Audit│
├────────┬────────┬────────┬─────────┤
│OpenClaw│ Claude │ Codex │ Cursor │
│ Agent │ Code │ Agent │ Agent │
└────────┴────────┴────────┴─────────┘
▲ heartbeats ▲ heartbeats ▲
Features
- Bring Your Own Agent — Any agent, any runtime, one org chart. If it can receive a heartbeat, it's hired.
- Goal Alignment — Every task traces back to the company mission. Agents know what to do and why.
- Heartbeats — Agents wake on a schedule, check work, and act. Delegation flows up and down the org chart.
- Cost Control — Monthly budgets per agent. When they hit the limit, they stop. No runaway costs.
- Multi-Company — One deployment, many companies. Complete data isolation. One control plane.
- Ticket System — Every conversation traced. Every decision explained. Full tool-call tracing and immutable audit log.
- Governance — You're the board. Approve hires, override strategy, pause or terminate any agent at any time.
- Org Chart — Hierarchies, roles, reporting lines. Agents have a boss, a title, and a job description.
- Mobile Dashboard — Manage autonomous businesses from your phone.
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.
- 1mo ago First seen · 107 lines · 56 tokens per session scan A faa5fca769e3
paperclip is a skill published in the GitHub repository amanning3390/hermeshub (48 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 1,195 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.