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 skills/racecraft-lab/paddock/panelsnpx skills add racecraft-lab/Paddock --skill panelsgit clone --depth 1 https://github.com/racecraft-lab/PaddockWrote 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/racecraft-lab/paddock/panels)<a href="https://agentmods.dev/skills/racecraft-lab/paddock/panels"><img src="https://agentmods.dev/badge/skills/racecraft-lab/paddock/panels.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.00020 | $0.01363 |
| Opus 5 | $0.00010 | $0.00681 |
| Sonnet 5 | $0.00004 | $0.00273 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
panels 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Panels
727 symbols | 76 files | Cohesion: 75%
When to Use
- Working with code in
src/ - Understanding how appendScopeToPath, fetchProjects, exportClientCsv work
- Modifying panels-related functionality
Key Files
| File | Symbols |
|---|---|
src/components/panels/office-panel.tsx |
formatLastSeen, easeInOut, getStatusEmote, inferLocalRole, getPropSprite (+41) |
src/components/panels/agent-detail-tabs.tsx |
handleSendMessage, handleSave, fetchTasks, fetchActivities, loadWorkspaceDocs (+37) |
src/components/panels/task-board-panel.tsx |
handleClick, handleSpawn, fetchReviews, fetchComments, handleAddComment (+32) |
src/components/panels/channels-panel.tsx |
ChannelsPanel, fetchChannels, handleProbe, handleAction, onProbe (+27) |
src/components/panels/cron-management-panel.tsx |
getAgentColorClass, isSameDay, formatDateLabel, CronManagementPanel, formatRelativeTime (+27) |
src/components/panels/memory-browser-panel.tsx |
mergeDirectoryChildren, fetchTree, loadFileTree, loadFileContent, toggleFolder (+26) |
src/components/panels/cost-tracker-panel.tsx |
buildGovernancePath, formatNumber, formatCost, getModelDisplayName, CostTrackerPanel (+18) |
src/components/panels/gateway-config-panel.tsx |
defaultValueFor, deepSet, matchesSearch, GatewayConfigPanel, fetchSchema (+18) |
src/components/panels/token-dashboard-panel.tsx |
exportClientCsv, TokenDashboardPanel, loadUsageStats, loadTrendData, loadSessionCosts (+16) |
src/components/panels/agent-squad-panel-phase3.tsx |
syncFromConfig, fetchAgents, updateAgentStatus, wakeAgent, toggleAgentHidden (+15) |
Entry Points
Start here when exploring this area:
appendScopeToPath(Function) —src/types/product-line.ts:120fetchProjects(Function) —src/store/index.ts:1006exportClientCsv(Function) —src/components/panels/token-dashboard-panel.tsx:204handleSpawn(Function) —src/components/panels/task-board-panel.tsx:681fetchTree(Function) —src/components/panels/memory-browser-panel.tsx:145
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 · 94 lines · 20 tokens per session scan A e0ebca17100c
panels is a skill published in the GitHub repository racecraft-lab/Paddock (11 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 1,363 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-08-30.
Other skills, from other repositories
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
unleash
Run as a named worker draining the task queue in my private coordination repo, where each task is a GitHub Issue — claim one task at a time, check blocked-by dependencies, plan with explicit assumptions, execute, validate against acceptance criteria, and record results as comments; then stay in ambush behind a…
status
Read-only console of a kraken queue — everything the operator reads in one place. Runs kraken.py status, which computes the review queue (awaiting-merge, with PR links), the decision queue (needs-decision), what is still in flight (every live claim ref — worker name + lease age, flagging expired leases), a…
init
Stand up a kraken coordination repo end to end — verify or create the private repo, install the bundled task template, remove everything an earlier release installed to be executed server-side, and create the canonical labels. Strictly setup, the write-side twin of status's read-only console; it reads and writes no…
nextjs-app-router-dev
Next.js App Router 开发与排障：Edge middleware、SQLite、session 认证。.
refactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.