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 instructions/restarter/lets-workflow/claude-mdgit clone --depth 1 https://github.com/restarter/lets-workflowWhat 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.12409 | $0.12409 |
| Opus 5 | $0.06205 | $0.06205 |
| Sonnet 5 | $0.02482 | $0.02482 |
| Haiku 4.5 | $0.01241 | $0.01241 |
Grade A, and why
lets-workflow CLAUDE.md scanned grade A 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Actor meta-agent loads personalities at runtime via internal skill `actor-fetch-personality`. Command fetches personality content (curl for URLs, Read for files), user confirms via review gate, actor receives it in pro How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lets-workflow
Claude Code plugin for development workflow with session management, code review, and task tracking.
Structure
Monorepo layout: plugin source in plugins/lets/ subdirectory, marketplace manifest at root pointing into it. Infrastructure scripts and docs stay at root, outside the plugin payload.
.claude-plugin/marketplace.json # Marketplace manifest (source: ./plugins/lets)
plugins/lets/ # Plugin payload (everything ${CLAUDE_PLUGIN_ROOT} resolves to)
├── .claude-plugin/plugin.json # Plugin manifest (Claude Code; .codex-plugin/ planned for multi-agent)
├── commands/ # Slash commands (/lets:start, /lets:done, /lets:review, etc.)
├── agents/ # 15 expert agents (review/opinion/ask/plan/backlog/team; skeptic verifies review findings + research claims)
├── skills/ # Reusable skills (user-facing auto-triggered + internal referenced by commands)
├── rules/ # Workflow rules (lets-rules.md) + tracker adapters (tracker-{beads,none}.md + TEMPLATE) - frontmatter-versioned, installed to .claude/rules/ by `lets init`
└── hooks/ # SessionStart + PreCompact hooks (drift check + LETS Config only - no rules in stdout)
cli/ # Go CLI - companion binary (Phase 2+, lets-7vtaw)
├── cmd/lets/main.go # Entry point (thin)
├── internal/cli/ # Cobra command factories (root.go, version.go, *_test.go)
├── internal/version/version.go # Version (var, ldflags-overridable from git tag)
├── go.mod, go.sum
└── .golangci.yml # golangci-lint v2 config (default linters + misspell; gofmt/goimports as formatters)
Makefile # Repo-root build (build/test/vet/lint/fmt/install/clean)
.editorconfig # Editor whitespace/charset settings
.github/workflows/ # CI: ci.yml (Go build/vet/test/lint on PRs+pushes), verify-versions.yml (source-tree version coherence), release.yml (tag-driven goreleaser)
scripts/dev/ # Dev workflow helpers (make dev / dev-tmux)
scripts/release/ # Release tooling: bump-version.sh + verify-versions.sh (used by Makefile bump/release-tag)
scripts/remote/dolt/ # Dolt SQL server VPS deployment + ad-hoc backup (NOT plugin)
scripts/remote/beads-web/ # beads-web (Rust kanban board) VPS deployment (NOT plugin)
scripts/deprecated/ # Retired scripts kept for cleanup runbooks - gitignored, not tracked
docs/ # Public-facing docs (installation.md, commands.md, workflow.md, agents.md, autonomous.md, commands/ per-command pages, …) + images/; planning notes / comment exports / KB live in gitignored docs-local/
reference/ # Local-only reference materials (gitignored)
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.
- 2d ago First seen · 239 lines · 12,409 tokens per session scan A c2ec66581399
lets-workflow CLAUDE.md is an instructions file published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 10d ago), licensed MIT. It adds 12,409 tokens to every session, about $0.0620 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
ii-agent AGENTS.md
Instructions for Intelligent-Internet/ii-agent, covering ii-agent contributor guide, quick start, repository map, mandatory rules and architecture.
spellbook AGENTS.md
Instructions for majiayu000/spellbook, covering spellbook agent contract, routing, scope rules, threads long-run guardrails and validation.
open-supermarkets AGENTS.md
Instructions for abracadabra50/open-supermarkets, covering agent integration guide, supported frameworks, quick integration, 1. add as skill and 2. agent calls commands.
helm copilot-instructions.md
Instructions for PetePeter/helm, covering gamepad-cli-hub — copilot instructions, project purpose, system overview, data flow pipeline and key controls.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
fusion-skills AGENTS.md
AGENTS.md instructions for CrowdStrike/fusion-skills, covering agents.md, what this is, prerequisites, repository structure and skills ecosystem.