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 robertbarclayy/conducty --skill conducty-tersegit clone --depth 1 https://github.com/robertbarclayy/conductyWrote 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/robertbarclayy/conducty/conducty-terse)<a href="https://agentmods.dev/skills/robertbarclayy/conducty/conducty-terse"><img src="https://agentmods.dev/badge/skills/robertbarclayy/conducty/conducty-terse/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/robertbarclayy/conducty/conducty-terse"><img src="https://agentmods.dev/badge/skills/robertbarclayy/conducty/conducty-terse.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.00115 | $0.01561 |
| Opus 5 | $0.00057 | $0.00781 |
| Sonnet 5 | $0.00023 | $0.00312 |
| Haiku 4.5 | $0.00012 | $0.00156 |
Grade A, and why
conducty-terse 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conducty Terse — Compression for Orchestration Artifacts
Caveman energy applied to conducty surface area. Prompts dispatched to subagents, prompt blocks in plan notes, entries in [[Prompt Log]], checkpoint notes — these are the artifacts where extra words cost twice: they bloat your orchestrator window AND every dispatched subagent's window.
This skill is the mechanical follow-through to the Conducty principle that prompt quality is leverage. Smaller prompts mean larger usable subagent context windows, which means more room for actual code, file reads, and verification output.
Scope — what gets compressed
| Artifact | Apply terse? | Reason |
|---|---|---|
| Subagent prompt text (Task tool input) | Yes | Every word costs once in your context, again in the subagent's |
| Plan note prompt blocks | Yes | Re-read on every dispatch; bloat compounds |
[[Prompt Log]] entries |
Yes | Append-only; the file grows forever |
| Checkpoint notes | Yes | Read by [[conducty-improve]] later |
| Orchestrator status updates to user | Yes | Match the user's caveman mode if active |
| Subagent reasoning / output | No | Subagents write in their own register |
| Acceptance criteria | No | Precision > brevity |
| No-go zones | No | Ambiguity = scope creep |
| Verification commands | No | Exact strings, never paraphrase |
| Error messages quoted | No | Verbatim or useless |
| Code, commits, PRs | No | Same boundary as caveman |
| Security warnings, destructive op confirmations | No | Auto-clarity rule |
Compression rules
Drop: articles (a/an/the), filler (just/really/simply/basically/actually), pleasantries (sure/certainly/please/happy to), hedging (might/perhaps/it seems), narrative throat-clearing ("In order to...", "It is important to note that...", "The reason we're doing this is..."), redundant restatement of plan context the subagent already has.
Keep exact: technical terms, file paths, error strings, command invocations, model names (haiku/sonnet/opus), type signatures, link targets ([[wikilink]]), acceptance criteria text, no-go zone text, verification command strings.
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 · 111 lines · 115 tokens per session scan A 19a481495533
conducty-terse is a skill published in the GitHub repository robertbarclayy/conducty (176 stars, last pushed 2mo ago), licensed MIT. It adds 115 tokens to every session and 1,561 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…