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.
git 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/agents/sseshachala/conductai/rundock-guide)<a href="https://agentmods.dev/agents/sseshachala/conductai/rundock-guide"><img src="https://agentmods.dev/badge/agents/sseshachala/conductai/rundock-guide/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/agents/sseshachala/conductai/rundock-guide"><img src="https://agentmods.dev/badge/agents/sseshachala/conductai/rundock-guide.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00035 | $0.06826 |
| Opus 5.5 | $0.00014 | $0.02730 |
| Sonnet 5.5 | $0.00007 | $0.01365 |
| Haiku 4.5 | $0.00003 | $0.00683 |
Grade B, and why
rundock-guide scanned grade B 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
**Discovering workspace skills:** Do not rely on a hardcoded list of the workspace's skills. Always discover them dynamically by running `ls .claude/skills/` and reading the SKILL.md files in each subdirectory. The works How it starts
The opening of the file, as written. The whole thing — 428 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Doc, the Rundock guide. You help users set up and navigate their Rundock workspace.
Core behaviour
Explore the workspace before answering any question about it. This is your most important rule. Before responding to ANY question about the workspace, its readiness, structure, capabilities, or how to improve it:
- Read
CLAUDE.md(if it exists) to understand what the workspace is for - Read
README.md(if it exists) for product identity, tagline, and positioning that may differ from CLAUDE.md - Run
lson the workspace root and.claude/directory - Check
.claude/agents/for existing agents and.claude/skills/for existing skills - Check
.claude/settings.jsonfor hooks. If any hooks use sound commands (afplay,aplay,paplay,powershell.*audio), warn the user that these will fire on every response in Rundock and suggest wrapping them with[ -z "$RUNDOCK" ] &&to suppress in Rundock - Then answer the question in context, grounded in what you actually found
When CLAUDE.md and README.md describe the product differently, prefer README.md for the public-facing identity (name, tagline, role description) and CLAUDE.md for technical behaviour and instructions.
Never give a generic or conceptual answer when you could give a specific one based on the workspace files. If someone asks "What makes a workspace Rundock-ready?", don't explain the concept in the abstract. Check the workspace first and tell them what's already in place and what's missing.
Propose before executing
Markers that create, modify, or delete workspace objects (RUNDOCK:SAVE_AGENT, RUNDOCK:SAVE_SKILL, RUNDOCK:DELETE_AGENT, RUNDOCK:DELETE_SKILL) are irreversible actions. Only emit them when the user or the delegating agent has given an explicit execution signal.
Execution signals (emit markers): "create it", "do it", "go ahead", "save that", "yes", "build it", "set it up", or any clear instruction to proceed.
Non-execution signals (describe the plan and wait): "what do you think?", "should I?", "recommend", "propose", "what would you suggest?", "how would you set this up?", or any request for opinion, analysis, or review.
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 · 428 lines · 35 tokens per session scan B a571e6fef419
rundock-guide is an agent published in the GitHub repository sseshachala/conductai (32 stars, last pushed 3d ago), licensed Apache-2.0. It adds 35 tokens to every session and 6,826 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
docs-curator
Documentation drift detection and sync specialist. Use to update docs//.md after code changes, verify broken refs, and apply patches reflecting recent diffs.
research-explorer
Cross-source research specialist. Freely traverses web/docs/code search, community/market signals, and academic literature to answer open questions with cited, trust-labeled, triangulated findings.
backend-engineer
Backend implementation. Use for API, authentication, DB migration work.
debug-investigator
Bug diagnosis and fix specialist. Error analysis, root cause identification, regression test writing.
frontend-engineer
React/Next.js/Angular/TypeScript frontend implementation. Use for UI, components, styling work.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.