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/akiojin/skills/inkjs-cligit clone --depth 1 https://github.com/akiojin/skillsWhat 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.00009 | $0.00643 |
| Opus 5 | $0.00005 | $0.00321 |
| Sonnet 5 | $0.00002 | $0.00129 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
inkjs-cli 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ink.js CLI Design Command
This command provides access to Ink.js (React for CLI) design patterns and implementation guidance.
Usage
/cli-design:inkjs-cli [topic]
Available Topics
Component Design
component- Component classification and patternsscreen- Screen component patternspart- Part component patternscommon- Common input component patterns
Patterns & Techniques
navigation- Multi-screen navigation patternsanimation- Spinner and progress bar patternsstate- State management patternslayout- Responsive layout patternsperformance- Performance optimizationinput- Input handling patterns
Troubleshooting
gotchas- Common issues and solutionsemoji- Emoji/icon width handlingctrlc- Ctrl+C handlinguseinput- useInput conflict resolution
Testing
testing- ink-testing-library patterns
Examples
Get component patterns
/cli-design:inkjs-cli component
Troubleshoot emoji width issues
/cli-design:inkjs-cli emoji
Learn about multi-screen navigation
/cli-design:inkjs-cli navigation
Quick Reference
Component Classification
| Type | Purpose | Key Features |
|---|---|---|
| Screen | Full-page view | useInput, Header/Content/Footer |
| Part | Reusable element | React.memo, pure/stateless |
| Common | Input component | Controlled/uncontrolled modes |
Directory Structure
src/cli/ui/
├── components/
│ ├── App.tsx # Root component
│ ├── common/ # Common components
│ ├── parts/ # Part components
│ └── screens/ # Screen components
├── hooks/ # Custom hooks
├── utils/ # Utilities
└── types.ts # Type definitions
Essential Hooks
| Hook | Purpose |
|---|---|
useInput |
Keyboard input handling |
useApp |
App lifecycle (exit) |
useFocus |
Focus management |
useStdin |
Raw stdin access |
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 · 105 lines · 9 tokens per session scan A 67fb4eb9ba3a
inkjs-cli is a command published in the GitHub repository akiojin/skills (8 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 643 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
design-to-code
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
a11y-audit-react
Identify accessibility violations in React components and provide actionable remediation aligned with WCAG 2.2 Level AA. This is the guided audit workflow that applies the standards defined in the a11y-automation and react-components rules.
get-component-source
The full TSX source of a component (append " demo" for its usage example).
pcc-ui-capability-card
Generate a PCC Capability Card React component using the @pcc/ui Solarpunk design system.
nextjs-cache
Get guidance on Next.js Cache Components setup.