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 agentmods add skills/coltonbearden/carrel/agent-workflowsnpx skills add coltonbearden/carrel --skill agent-workflowsgit clone --depth 1 https://github.com/coltonbearden/carrelWrote 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/coltonbearden/carrel/agent-workflows)<a href="https://agentmods.dev/skills/coltonbearden/carrel/agent-workflows"><img src="https://agentmods.dev/badge/skills/coltonbearden/carrel/agent-workflows.svg" alt="Measured on agentmods" 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 | $0.00058 | $0.00635 |
| Opus 5 | $0.00029 | $0.00318 |
| Sonnet 5 | $0.00012 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
agent-workflows 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 4d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent workflows with carrel
Patterns for wiring carrel and Claude Code together into pipelines. Run carrel doctor --json first to see what the environment supports, and --help on any carrel command before scripting it.
Pattern: watch + claude -p pipeline
React to new files with a headless Claude turn. Example — summarize every PDF dropped into a folder:
carrel watch ~/inbox --on created --glob '*.pdf' \
--run 'sh -c "carrel convert {path} --to txt -o /tmp/drop.txt --force && claude -p \"Summarize /tmp/drop.txt in 5 bullets\" >> ~/inbox/summaries.md"'
Notes: keep the claude -p prompt self-contained; append results to a log/markdown file; test with --once --timeout 60 before leaving it running. (Confirm carrel watch exists in the installed version.)
Pattern: index-then-ask loop
For question-answering over a collection, keep one desk index and reuse it:
carrel --json --root ~/papers index # incremental, cheap to re-run
carrel --json --root ~/papers search 'transformer AND survey'
Feed the hit paths to Claude (or the file-librarian agent in this plugin) rather than packing the whole corpus — search first, read the top hits, cite paths.
Pattern: desk over MCP
This plugin ships a carrel MCP server (carrel mcp, stdio) exposing search, pack, and inspect as tools. When it's connected, prefer the MCP tools over shelling out for those three operations — same results, structured output. The server searches the desk under the session's working directory; run carrel index there first.
Pattern: pack for a second opinion
Bundle context for another model/session: carrel pack DIR --format xml --chunk 40000 -o ctx.xml then feed ctx.xml.part1..N sequentially. See the context-packing skill (carrel-inspect plugin) for budgeting guidance.
Hygiene for all loops
- Idempotence: carrel index is incremental and
--if-indexedmakes hook-style reindexing a no-op until a desk exists — loops can run unconditionally. - Never delete in a loop:
carrel dedupestays report-only unless both--deleteand--applyare passed; keep automation on the report side. - Budget: bound every unattended loop with
--timeout, log with--json-lines, and route long outputs to files, not the terminal.
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.
- 4d ago First seen · 45 lines · 58 tokens per session scan A e824a5ff5f26
agent-workflows is a skill published in the GitHub repository coltonbearden/carrel (1 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 635 once invoked, about $0.0003 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-31.
Other skills, from other repositories
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
shipping-artifacts
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded…
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
competitive-battlecard
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'.