Paperclip is a Node.js server and React application for coordinating AI agents as a business team, with goals, organizational roles, budgets, governance, and work tracking in one interface. It is used by people managing multiple agents or autonomous agent organizations across tools such as OpenClaw, Claude Code, Codex, and Cursor. The catalogue includes skills, agents, an MCP add-on, and an instruction for working with Paperclip.
Borrowing it
Nothing to install: this file belongs to paperclipai/paperclip. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/paperclipai/paperclip/master/.agents/skills/create-issue-interaction-ui/SKILL.mdgit clone --depth 1 https://github.com/paperclipai/paperclipWrote 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/paperclipai/paperclip/create-issue-interaction-ui)<a href="https://agentmods.dev/skills/paperclipai/paperclip/create-issue-interaction-ui"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/create-issue-interaction-ui/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/paperclipai/paperclip/create-issue-interaction-ui"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/create-issue-interaction-ui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 44 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Agent Snooping · line 210 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 256 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00044 | $0.03418 |
| Opus 5.5 | $0.00018 | $0.01367 |
| Sonnet 5.5 | $0.00009 | $0.00684 |
| Haiku 4.5 | $0.00004 | $0.00342 |
Grade A, and why
create-issue-interaction-ui 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 today.
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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a new issue-thread interaction UI (Developer/maintainer skill)
Developer/maintainer skill. Do NOT install this on production Paperclip agents.
This skill walks a Paperclip contributor through introducing a new issue-thread
interaction kind from shared contract to issue-detail wiring, helpers, and
docs. It is intentionally a developer/maintainer skill: the audience is a
human or coding agent making code changes inside paperclipai/paperclip, not
the operational agents that run inside a deployed Paperclip company.
Do NOT install this on production Paperclip agents. This guide is for repository contributors changing Paperclip itself.
When to use
- A new interaction kind is being introduced (compact picker, structured rating, in-thread approval card, etc.).
- An existing interaction needs a parallel variant with a distinct payload
shape, validation, or resolution outcome (and
ask_user_questionsis the wrong fit because option count, target binding, or result shape differs). - A reviewer asks for "the same audit, staleness, supersede, and continuation semantics as the other interactions" on a new card.
When NOT to use
- Adding fields to an existing interaction kind that does not need a new payload schema. Patch the existing validators/UI in place instead.
- Changing how Paperclip agents call interactions. Update
skills/papercliporreferences/api-reference.md; that is agent guidance, not card work. - Building a non-thread UI (issue detail sidebar, project board widget, etc.). Those have their own component conventions.
Mental model
Every issue-thread interaction has five moving parts:
| Layer | Owns |
|---|---|
| Shared | Kind constant, payload/result interfaces, Zod validators, exported types, shared-test coverage. |
| Server | Service create/accept/reject/respond, staleness, supersede, idempotency, activity log, wake send. |
| UI | Card pending/resolved/stale states, fixtures, Storybook, issue-thread/IssueDetail wiring. |
| Channels | Complete question/context, native response or Paperclip handoff, callback authorization, and settled provider cards. |
| Helpers/Docs | CLI command, MCP tool, plugin SDK type+host+testing path, skills/paperclip guidance. |
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.
- today Changed · +25 lines 8d64dd458b80
- 12d ago Changed 024aa2582906
- 1mo ago First seen · 276 lines · 44 tokens per session scan A 721819ad168f
create-issue-interaction-ui is a skill published in the GitHub repository paperclipai/paperclip (107,044 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 3,418 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
fleetq-connect
Connect an agent to FleetQ over MCP or the REST API, including obtaining credentials via dynamic client registration.
fleetq-manage-workflow
Build, validate, cost, and execute FleetQ visual DAG workflows — including generating one from a natural-language goal.
fleetq-run-experiment
Create, run, monitor, and recover a FleetQ experiment through its 20-state pipeline via MCP tools or the REST API.
atelier
Operate the Atelier software factory (the ADW engine stamped into this repo's adws/). Use when the user says /atelier, wants to create / run / update an ADW or workflow, manage the agent roster in sssf.config.yaml, keep the engine current, or observe running agent workflows. Keywords - atelier, software factory, ADW…
deep-reasoning
Structured multi-step reasoning tool for complex problem solving with branching, hypothesis testing, and evidence tracking.
app-launcher
Launch applications, open URLs in browser, and list running processes. Requires approval for launching applications.