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 aaronjmars/aeon-agent --skill feedback-buildergit clone --depth 1 https://github.com/aaronjmars/aeon-agentWrote 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/aaronjmars/aeon-agent/feedback-builder)<a href="https://agentmods.dev/skills/aaronjmars/aeon-agent/feedback-builder"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/feedback-builder/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/aaronjmars/aeon-agent/feedback-builder"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/feedback-builder.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.00045 | $0.03468 |
| Opus 5.5 | $0.00018 | $0.01387 |
| Sonnet 5.5 | $0.00009 | $0.00694 |
| Haiku 4.5 | $0.00005 | $0.00347 |
Grade A, and why
feedback-builder 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 10d 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.
This is a copy
100% identical to feedback-builder — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} - Source selector. Empty = every source in
memory/feedback-sources.md.<feedback-url> <owner/repo>= one-shot run on that endpoint and repo (config file ignored). Prefixdry-run:to fetch and triage only, no branch or PR (e.g.dry-run:ordry-run:<feedback-url> <owner/repo>). Append--max Nto build up to N PRs this run (default 1, hard ceiling 3).
Agents are now the heaviest users of most APIs. When one hits a bug or a missing feature, the service's /feedback endpoint records it in a structured way. This skill closes the loop: it reads those reports, decides which ones make sense, and drafts the code change as a PR. A human approves by merging. This skill never merges.
Today is ${today}. Read memory/MEMORY.md and the last 3 days of memory/logs/ before starting.
Phases
PREFLIGHT -> FETCH -> NORMALIZE -> RECONCILE -> TRIAGE -> BUILD -> STATE -> NOTIFY -> LOG
Exit taxonomy
Pick exactly one before notifying.
| Code | Meaning |
|---|---|
FEEDBACK_OK_BUILT |
At least one PR opened from accepted feedback |
FEEDBACK_OK_TRIAGED |
New feedback triaged, nothing built (no BUILD verdict, or build failed its checks) |
FEEDBACK_CAPPED |
BUILD candidates exist but the open-PR cap blocked every one |
FEEDBACK_NO_NEW |
Sources reachable, no new or changed items |
FEEDBACK_DRY_RUN |
dry-run: - triage only |
FEEDBACK_NO_CONFIG |
No ${var} and no usable memory/feedback-sources.md |
FEEDBACK_SOURCE_ERROR |
Every source failed to fetch |
Config
memory/feedback-sources.md - operator-owned, never edit it here. One source per line, <feedback-url> -> <owner/repo>. Bullets are fine; lines starting with # are ignored.
# Feedback sources
- <feedback-url> -> owner/api-repo
- <feedback-url> -> owner/other-service
If ${var} is empty and the file is missing or has no valid lines, log FEEDBACK_NO_CONFIG and exit cleanly. Send no notification: empty config is not an error.
FEEDBACK_TOKEN (optional) - sent as Authorization: Bearer to every source. Leave it unset for public endpoints. One token covers all sources.
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.
- 10d ago First seen · 255 lines · 45 tokens per session scan A cbe22fc5bddf
feedback-builder is a skill published in the GitHub repository aaronjmars/aeon-agent (12 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 3,468 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to feedback-builder, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
project-flow-ops
CIEL's coordination layer for triaging issues, PRs, and tasks across GitHub and internal tracking systems (e.g., Linear).
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
git-commit
Stage, write, and structure git commits and pull requests cleanly. Read this before committing — for conventional-commit message format, when to split commits, and how to open a PR with the gh CLI.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.