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 GumbyEnder/agent-relay --skill devboardsgit clone --depth 1 https://github.com/GumbyEnder/agent-relayWrote 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/gumbyender/agent-relay/devboards)<a href="https://agentmods.dev/skills/gumbyender/agent-relay/devboards"><img src="https://agentmods.dev/badge/skills/gumbyender/agent-relay/devboards/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/gumbyender/agent-relay/devboards"><img src="https://agentmods.dev/badge/skills/gumbyender/agent-relay/devboards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Data Exfiltration · line 78 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00013 | $0.01513 |
| Opus 5.5 | $0.00005 | $0.00605 |
| Sonnet 5.5 | $0.00003 | $0.00303 |
| Haiku 4.5 | $0.00001 | $0.00151 |
Grade A, and why
devboards scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS -X POST -H "Authorization: Bearer $KEY" -H "content-type: application/json" \ How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Boards — client agent
You are a remote client. You only talk to Dev Boards over HTTPS. You do not need GitHub, a local checkout of Dev Boards, or the operator UI.
Canonical surfaces (always current on the live app — not Hermes kanban):
- UI: open ? (help) or Agents → Client agent README
- Guide:
GET https://app.devboards.ai/api/agent/client-guide - This skill:
GET https://app.devboards.ai/api/agent/skill.md
Prerequisites
Human sets secrets in your runtime (not in chat):
DEVBOARDS_BASE_URL=https://app.devboards.ai
DEVBOARDS_API_KEY=ark_…
DEVBOARDS_AGENT=your-registered-name
DEVBOARDS_BOARD=zeeva-mobile # board slug or board_… id — both work
Not Hermes kanban. hermes kanban and t_… task ids are a different product. Dev Boards missions are msn_… via HTTPS only.
Job loop (ticket counter / process)
Treat the board as the source of truth. Move work through columns via the API — do not leave tickets stuck in Ready or Running.
- File — when the human asks you to create work →
POST /missions(default inbox; Ready only if told) - Poll Ready —
GET /missions?column=ready&limit=5&agent=$AGENT&project=$BOARD - Claim one —
POST …/claim(required before implementation; no 200 → no work) - Work — implement with tools you already have
- Heartbeat — while working (every ~2–5 minutes or at each meaningful milestone)
- Deliver —
POST …/deliverwith summary + optional usage → ticket goes to Review - Or escalate — one clear question → Needs human
Batch discipline
- Prefer 3–8 Ready tickets per session when the human says “work Ready,” not the entire column.
- Finish (deliver/escalate) what you claimed before claiming the next.
- After deliver, the ticket is in Review — human accepts. Do not re-claim it.
- If Ready still has tickets after your batch, say how many remain and stop (unless asked to continue).
- Empty Ready and no “file work” request → stop and say so.
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 · 135 lines · 13 tokens per session scan A a1f173f81f39
devboards is a skill published in the GitHub repository GumbyEnder/agent-relay (40 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 1,513 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
kaneo-cli
Work with Kaneo tasks, projects, comments and time tracking through the kaneo CLI. Use when the user asks to list, create, update, assign or close Kaneo tasks, see what is assigned to them, comment, log time, or script against a Kaneo workspace on Kaneo Cloud or a self-hosted instance.
omh-research-department
This is a Hermes-native research-department workflow skill.
omh-agent-board
This is a Hermes-native agent-board workflow skill.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
bo-process-optimization
A method for examining a business workflow to find waiting, rework, handoff waste, and other delays, then proposing improvements and ways to measure them. It separates observed facts from possible explanations and suggestions.