Borrowing it
Nothing to install: this file belongs to advenimus/conduit-desktop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/advenimus/conduit-desktop/main/.claude/commands/dev.mdgit clone --depth 1 https://github.com/advenimus/conduit-desktopWrote 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/commands/advenimus/conduit-desktop/dev)<a href="https://agentmods.dev/commands/advenimus/conduit-desktop/dev"><img src="https://agentmods.dev/badge/commands/advenimus/conduit-desktop/dev/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/commands/advenimus/conduit-desktop/dev"><img src="https://agentmods.dev/badge/commands/advenimus/conduit-desktop/dev.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.00000 | $0.00737 |
| Opus 5.5 | $0.00000 | $0.00295 |
| Sonnet 5.5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
dev 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 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.
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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conduit Development Workflow
You are continuing development on Conduit, an AI-powered remote connection manager. Follow this workflow precisely.
Step 1: Read Documentation
Read these files to understand current state:
docs/PROGRESS.md- Check milestone status and task completiondocs/TECHNICAL_SPEC.md- Understand architecture (if needed)- Identify the current phase from PROGRESS.md (first phase with incomplete tasks)
- Read the corresponding phase doc:
docs/phases/PHASE_XX_*.md
Step 2: Assess Current State
Before writing any code:
- Check what exists: Use Glob/Grep to see what files/code already exist
- Identify the next incomplete task from the current phase
- Understand dependencies: What must exist before this task can be done?
Step 3: Implement
For each task:
- Implement the code following the phase documentation
- Follow existing patterns - check similar existing code first
- Keep changes focused - one task at a time
Step 4: Verify (CRITICAL)
After implementing each task, you MUST verify it works:
For Rust Code:
# Check it compiles
cargo check --workspace
# Run tests for the specific crate
cargo test -p <crate-name>
# If no tests exist yet, at minimum verify compilation
cargo build --workspace
For Frontend Code:
# Check TypeScript compiles
npm run build
# Run tests if they exist
npm test
For Tauri Integration:
# Verify the app launches
cargo tauri dev
Troubleshooting:
- If compilation fails, fix errors before proceeding
- If tests fail, fix them before marking complete
- If runtime errors occur, debug and resolve
- Document any blockers in PROGRESS.md
Step 5: Update Progress (Only After Verification)
Only after a task is verified working:
-
Update
docs/PROGRESS.md:- Change task status from 🔴 to 🟢
- Add any notes about the implementation
- If blocked, mark as 🔵 and document the blocker
-
If the entire phase is complete:
- Update the milestone status in the Quick Status table
- Add a note in the "Notes & Updates" section
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 · 108 lines · 0 tokens per session scan A 37958c5e74d8
dev is a command published in the GitHub repository advenimus/conduit-desktop (19 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 737 tokens. 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 commands, from other repositories
cargo-metadata
Command "cargo-metadata" from olorehq/olore, covering cargo-metadata(1), name, synopsis, description and output format.
mutation-test
Uses cargo-mutants to run mutation tests and verify test quality.
cargo-bench
Command "cargo-bench" from olorehq/olore, covering cargo-bench(1), name, synopsis, description and working directory of benchmarks.
cargo-build
Command "cargo-build" from olorehq/olore, covering cargo-build(1), name, synopsis, description and options.
cargo-check
Command "cargo-check" from olorehq/olore, covering cargo-check(1), name, synopsis, description and options.
cargo-fetch
Command "cargo-fetch" from olorehq/olore, covering cargo-fetch(1), name, synopsis, description and options.