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 commands/matrixfounder/agentic-development/run-feedbackgit clone --depth 1 https://github.com/MatrixFounder/Agentic-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/commands/matrixfounder/agentic-development/run-feedback)<a href="https://agentmods.dev/commands/matrixfounder/agentic-development/run-feedback"><img src="https://agentmods.dev/badge/commands/matrixfounder/agentic-development/run-feedback.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.00000 | $0.00250 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
run-feedback 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 today.
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.
What it actually says
Read and apply the skill defined in .agent/skills/run-feedback/SKILL.md in ad-hoc mode
(§7 "Ad-hoc" — no claim/release):
- If the scope hint below contains
mine, first run the transcript miner (python3 .agent/skills/run-feedback/scripts/run_feedback.py mine --dry-run, review the candidate yield with the user, then re-run without--dry-runif approved). - Gather friction signals from the CURRENT session — failed commands, retries, exhausted gates,
escalations — plus
active_blockersfrom.agent/sessions/latest.yaml, scoped by the hint. - Ask the one retro question ("Что прошло НЕ гладко?") with observed candidates pre-listed,
then
collect→triage→ classify →file --dry-run→file, per the skill's §7 Triage protocol. - Finish with a one-line report: filed IDs, dismissed count, journal path.
Apply all Global Protocols (skill-session-state). This command is non-blocking feedback collection — it never modifies existing issues or code.
Scope hint (optional): $ARGUMENTS
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.
- today First seen · 19 lines · 0 tokens per session scan A bf2c9a64635c
run-feedback is a command published in the GitHub repository MatrixFounder/Agentic-development (5 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 250 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-09-03.
Other commands, from other repositories
plan-sprint
Run a design sprint end to end — challenge framing, schedule, exercises, and prototype test plan.
predict
Pre-implementation 5-persona adversarial analysis for high-stakes gflow-cli proposals. Produces a GO / CAUTION / STOP verdict before any code is written. Invoke before new transports, auth changes, selector redesigns, schema migrations, or any PLAN.md backlog item gated on an investigation step.
respond-to-issue
Respond to an issue triggered by @elixpoo mention or the ELIXPO label.
pm-agent-retire
Mark a great-pm agent as deprecated. Adds a deprecation banner to the agent file, files a Beads issue to remove dependent commands/workflows, and logs the rationale. NEVER deletes the file (history preserved).
pm-agent-review
Review a great-pm agent's recent verdict history. Shows verdict distribution (PASS/FAIL/NEEDS-WORK), trend over time, and whether the agent is drifting.
pm-audit
Run the great-pm PM-health audit on a product, an initiative, or great-pm itself. 15 dimensions, severity-rated findings, Top-5 + Quick-Wins + Things-Look-Bad-But-Fine + Open Questions. Files findings as Beads tasks unless --read-only.