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 jmagly/aiwg --skill feedbackgit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/feedback)<a href="https://agentmods.dev/skills/jmagly/aiwg/feedback"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/feedback/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/jmagly/aiwg/feedback"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/feedback.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.00025 | $0.01030 |
| Opus 5 | $0.00013 | $0.00515 |
| Sonnet 5 | $0.00005 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
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 9d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIWG Feedback
Submit a bug report, feature request, doc gap, or general feedback to the AIWG GitHub repository. System context (version, OS, provider, installed frameworks) is collected and prefilled automatically.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "report a bug" → bug report
- "something isn't working" → bug report
- "aiwg is broken" → bug report with doctor output
- "request a feature" → feature request
- "this feature is missing" → feature request
- "docs are wrong" / "doc gap" → documentation issue
- "file an issue" → issue submission (type selection prompt)
- "give feedback about aiwg" → general feedback
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Bug report | "report a bug with aiwg serve" | aiwg feedback --type bug |
| Feature request | "request a feature for aiwg" | aiwg feedback --type feature |
| Doc gap | "the docs for mcp inject are wrong" | aiwg feedback --type doc |
| General | "I have feedback" | aiwg feedback |
| With context | "file this as a bug: X" | Extract title/body, run aiwg feedback --type bug --title "..." --body "..." |
Behavior
When triggered:
-
Extract from conversation (if the user described the issue):
- Type: bug | feature | doc | other
- Title: short phrase summarizing the issue (max 80 chars)
- Body: structured description of what happened, what was expected
-
Run the appropriate command:
# Interactive (when type/title/body not clear from context) aiwg feedback # With extracted type aiwg feedback --type bug # Fully extracted from conversation aiwg feedback --type bug --title "doctor crashes when .aiwg missing" --body "Running aiwg doctor in a new project with no .aiwg directory causes an unhandled exception..." # Feature request aiwg feedback --type feature --title "add --watch flag to aiwg index build" --body "..." # Doc gap aiwg feedback --type doc --title "mcp inject workflow not documented" --body "..."
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.
- 9d ago First seen · 123 lines · 25 tokens per session scan A 3d11c27ade4a
feedback is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,030 once invoked, about $0.0001 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
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…
goal-writer
Drafts a goal+rider document pair that briefs an autonomous coding agent on one round of work — a goal file under 4,000 characters (sized to fit the /goal command in both Claude Code and Codex) plus an unbounded rider with phased plans and named depth tests. Use when the user says "draft a goal", "write a goal+rider"…
horizon
Run a durable Horizon workflow for a multi-feature goal with bounded autonomous retries and an audit trail.
check-in
Record a Parallax protocol checkpoint with concrete evidence before gated implementation work.
debug
Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
hyperplan
Harden a non-trivial plan through a three-round adversarial critique and evidence-based synthesis.