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 ShivaeDev/pardes --skill drive-workstreamgit clone --depth 1 https://github.com/ShivaeDev/pardesWrote 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/shivaedev/pardes/drive-workstream)<a href="https://agentmods.dev/skills/shivaedev/pardes/drive-workstream"><img src="https://agentmods.dev/badge/skills/shivaedev/pardes/drive-workstream/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/shivaedev/pardes/drive-workstream"><img src="https://agentmods.dev/badge/skills/shivaedev/pardes/drive-workstream.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.00048 | $0.00709 |
| Opus 5.5 | $0.00019 | $0.00284 |
| Sonnet 5.5 | $0.00010 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
drive-workstream 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 2mo 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drive Workstream
Manage a substantial coding objective from initial understanding through a sequence of reviewed pull requests. Keep the main session focused on decisions, durable state, delegation, and user communication. The manager coordinates the work but does not implement or review code itself.
Pipeline
- Clarify the objective and constraints.
- Use
investigate-codebaseto gather evidence with read-only explorers. - Discuss the evidence, architecture, scope, and PR sequence with the user. Do not begin implementation until the user approves the scope and sequence.
- Create a Markdown workstream note under:
${CODEX_ARTIFACTS_DIR:-$HOME/codex-artifacts}/workstreams/<repo-key>/<workstream>.md - For each approved PR:
- use
implement-change - use
verify-change - use
run-pr-cycle
- use
- After merge, sync the primary checkout with the repository's normal workflow, delete the completed PR's note, and continue the next approved PR automatically. If another approved PR remains, create a fresh minimal note for it before starting work.
Use references/workstream-note.md when creating or recovering a note.
Manager Rules
- Delegate code inspection to explorers, code changes to writing workers, and full diff review to fresh read-only verifiers.
- Do not edit source code, read complete diffs, or run implementation validation in the manager session.
- Own cheap metadata checks, worktree creation, durable state, publication, browser handoff, and blocking waits.
- Treat the workstream note as a disposable checkpoint, not a journal. Rewrite it in place with current state only. Do not append progress history.
- Use one owner worker per PR. Spawn supporting workers when independent chunks can proceed in parallel. The owner worker integrates accepted support commits.
- Keep the owner worker available for verifier, CI, and review feedback.
- Keep active worker branches on their assigned branch-point SHA. Movement on the target branch alone is not a reason to rebase or recreate them.
- Record newly discovered work outside the approved scope as candidate follow-ups. Do not ship it inline.
- Never merge unless explicitly asked.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 69 lines · 48 tokens per session scan A a09beec3f2d7
drive-workstream is a skill published in the GitHub repository ShivaeDev/pardes (5 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 709 once invoked, about $0.0002 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.