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-skillsgit 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-skills)<a href="https://agentmods.dev/skills/sseshachala/conductai/rundock-skills"><img src="https://agentmods.dev/badge/skills/sseshachala/conductai/rundock-skills/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/sseshachala/conductai/rundock-skills"><img src="https://agentmods.dev/badge/skills/sseshachala/conductai/rundock-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 37 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.
- medium Agent Snooping · line 6 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.00012 | $0.01022 |
| Opus 5 | $0.00006 | $0.00511 |
| Sonnet 5 | $0.00002 | $0.00204 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
Skill 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 11d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage skills in .claude/skills/. 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 skill files. Instead, use RUNDOCK markers. The Rundock client detects these markers in your response and saves the files through the server.
Create a skill
1. Understand the skill
Ask the user:
- What should this skill do? (purpose, when it triggers)
- Which agent should own it? (check
.claude/agents/for the current team)
If the user already provided enough detail, skip straight to drafting.
2. Draft the skill
A good skill file has:
- Clear trigger: When should the agent use this skill? Be specific about the user request or situation.
- Step-by-step instructions: Numbered steps, not prose paragraphs. Each step should be a concrete action.
- File references: Specific paths the skill reads from or writes to. Run
lsif unsure what exists. - Output format: What the result should look like (structure, length, tone).
- Boundaries: What the skill does NOT cover. Which other skill or agent handles adjacent requests.
Naming: Slugs are lowercase with hyphens: meeting-prep, weekly-digest, code-review.
3. Save the skill
Output the complete skill file wrapped in the marker:
---
name: {Human Readable Name}
description: {What this skill does}
---
{Skill instructions}
The skill will be saved to .claude/skills/{slug}/SKILL.md. The skills panel updates automatically.
4. Assign to an agent
After creating the skill, update the owning agent's instructions to reference the skill slug. This is how Rundock connects skills to agents in the UI.
Tell the user: "To connect this skill to [agent name], I need to update their instructions to reference {slug}. Want me to do that?"
If yes, read the agent file from .claude/agents/{agent-slug}.md, add the skill reference to the appropriate section, and output the updated agent file using:
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.
- 11d ago First seen · 120 lines · 12 tokens per session scan A c14a940f70f4
Skill Management is a skill published in the GitHub repository sseshachala/conductai (32 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 1,022 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
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 }}.
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 }}.
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.
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.
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
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 }} + {{…