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 OutlineDriven/outline-driven-development --skill feedback-sweepgit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/feedback-sweep)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/feedback-sweep"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/feedback-sweep/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/outlinedriven/outline-driven-development/feedback-sweep"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/feedback-sweep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.03920 |
| Opus 5 | $0.00030 | $0.01960 |
| Sonnet 5 | $0.00012 | $0.00784 |
| Haiku 4.5 | $0.00006 | $0.00392 |
Grade A, and why
feedback-sweep 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 5d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feedback sweep
Contract
| Field | Bound contract |
|---|---|
| Trigger | /feedback-sweep [setup |
| Authority | Reversible local writes: the repo-internal sweep state file, the feedback-sweep plan, source acknowledgements and close-outs on approved sources, commits and shared-branch pushes when sweep_shared_branch: true, and setup writes to .odin/config.local.yaml during first-run configuration. Roll back by reverting local paths and, for source-side writes, by reversing the ack or close-out action where the source supports it. No source-side write ever reaches a source whose config entry has approved: false. |
| Side effect | Reads configured feedback sources, acknowledges approved items at source, analyzes media under a private scratch directory, writes repo-internal sweep state and the plan, and emits an autopilot-ready handoff. Raw media is never committed. |
| Done | The run is recorded, the lease is released, and the summary is printed with the plan path and handoff invocation. |
Inputs
Arguments are optional: a setup or reconfigure token, and a mode:non-interactive token; strip it before routing.
Configuration is read from <repo-root>/.odin/config.local.yaml then .odin/config.yaml (<repo-root> = git rev-parse --show-toplevel); the first active value wins. For scalars, empty is unset and an invalid value continues to the next layer then the default; for lists and maps, a present key (including an empty list or map) replaces the whole key. docs_root is read from .odin/config.yaml only.
feedback_sources must be configured before a sweep run; its absence, or a setup/reconfigure token, routes to setup. Each source entry carries a type (slack, github-issues, email), its target, the standing-approved ack action, an optional close-out action, and an optional sensitive: true and approved: false. The sweep keys and defaults: sweep_state_path (fallback <root>/feedback-sweep/state.yml; a repo-internal path means committed mode, a path outside the repo means machine-local mode), sweep_lease_ttl_minutes (default 60), sweep_shared_branch (default false), sweep_ack_cap (default 25).
What ships with it
1 file 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.
- 5d ago First seen · 74 lines · 59 tokens per session scan A eff0345b4645
feedback-sweep is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 3d ago), licensed Apache-2.0. It adds 59 tokens to every session and 3,920 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-09-03.
Other skills, from other repositories
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
github-backlog-triage
Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.
setup-repo-skills
Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.
git-history-analysis
Use when the user asks about recent engineering work, what the team is working on, planning or roadmap material, or an explicitly requested Slack summary. Not for remote or irreversible changes.
atomic-issues-prs
Use when the user says "atomic PRs" or requests one issue or PR per logical change. Don't use for single-change pushes or uncommitted change-sets.
graph-backbone
Use when defining, revising, or gate-replanning the project structural backbone in project-root graph.yaml; produces a validated approved revision preserving immutable topology and additive metadata. Not for remote, credential, publish, deploy, or irreversible changes.