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 sseshachala/conductai --skill rundock-agentsgit clone --depth 1 https://github.com/sseshachala/conductaiWrote 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/sseshachala/conductai/rundock-agents)<a href="https://agentmods.dev/skills/sseshachala/conductai/rundock-agents"><img src="https://agentmods.dev/badge/skills/sseshachala/conductai/rundock-agents.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Prompt Injection · line 61 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00014 | $0.01691 |
| Opus 5 | $0.00007 | $0.00846 |
| Sonnet 5 | $0.00003 | $0.00338 |
| Haiku 4.5 | $0.00001 | $0.00169 |
Grade A, and why
Agent Management 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 8d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage agents in .claude/agents/. This skill covers the full lifecycle.
Important: file access
Claude Code blocks Write and Edit tools for files inside .claude/. Do NOT use Write, Edit, or Bash to create, modify, or delete agent files. Instead, use RUNDOCK markers. The Rundock client detects these markers in your response and saves the files through the server.
Create an agent
1. Gather details
Ask the user:
- What should this agent do? (responsibilities, domain)
- What should it be called? (suggest a slug name and display name)
- What type is it? (
orchestratororspecialist)
If the user already provided enough detail, skip straight to drafting.
2. Choose identity
Naming convention: The name (slug), filename, and role must all refer to the same thing. The slug is the hyphenated lowercase form of the role. Examples: role "Content Lead" = slug content-lead, role "Executive Assistant" = slug executive-assistant, role "Design Lead" = slug design-lead. The displayName is a separate, short human name unrelated to the role (e.g. "Penn", "Lea", "Des"). Never use the displayName as the slug.
Suggest and confirm:
- name (slug): Hyphenated lowercase form of the role. This becomes both the
namefield and the filename ({slug}.md). Must describe the role, not the person. - displayName: Short, memorable, character-style name. Good: "Dex", "Intel", "Kit". Bad: "Meetings Agent", "Project Tracker". Must not match or resemble the slug. The
rolefield carries the functional title. - role: 2-4 word title (e.g. "Meeting Intelligence", "Content Strategist"). The slug is derived from this.
- icon: Single unicode character. Must be visually distinct from existing agents.
- colour: Hex colour for avatar. Must be visually distinct from existing agents.
- order: 0 for orchestrator, sequential integers for specialists. Use decimals for sub-agents (e.g. 1.1, 1.2 under a lead at order 1). Check existing agents to avoid collisions.
- reportsTo: The
nameslug of the agent this one reports to. Every specialist should have this set. Direct reports of the orchestrator use the orchestrator's slug. Sub-agents use their lead's slug. - model:
opusfor orchestrator,sonnetfor most specialists
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.
- 8d ago First seen · 158 lines · 14 tokens per session scan A 97a3b12ddfb1
Agent Management is a skill published in the GitHub repository sseshachala/conductai (32 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 1,691 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
background-task
Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.
agent-tool
Add a new tool/function the AI agent can call (e.g. look something up, hit an external API, perform an action). Use when extending the assistant's capabilities, wiring a new function into the agent, or when the model needs a new action. This project uses {{ cookiecutter.aiframework }}.
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
rag-knowledge
Work with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vectorstore }} + {{…
alembic-migration
Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.
channel-bot
Work with messaging-channel bots (Telegram / Slack) — register a bot, route inbound messages through the AI agent, handle webhooks vs polling, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery.