Borrowing it
Nothing to install: this file belongs to vladm3105/aidoc-flow-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vladm3105/aidoc-flow-framework/dev/.agents/skills/submit-feedback/SKILL.mdgit clone --depth 1 https://github.com/vladm3105/aidoc-flow-frameworkWrote 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/vladm3105/aidoc-flow-framework/submit-feedback)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/submit-feedback"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/submit-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/vladm3105/aidoc-flow-framework/submit-feedback"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/submit-feedback.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.00056 | $0.01768 |
| Opus 5.5 | $0.00022 | $0.00707 |
| Sonnet 5.5 | $0.00011 | $0.00354 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
submit-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 1mo 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submit feedback
Muse-local instance of the submit-feedback workflow. Engine-agnostic wording follows
framework/skills/submit-feedback/(itself adapted from the canonaidoc-flow-claude-agents-config/skills/submit-feedback/SKILL.md); where the canon names a Claude-specific agent type or path, use the Muse equivalent below and keep the independence contract.
An actionable finding must survive the session that found it. Capture it on the owning repository's declared backlog surface; never leave it only in chat, scratch, a commit message, or a session handoff.
A finding also has to carry where it came from. A defect a real project hit and a defect a review pass went looking for read identically once written up, and the reader cannot recover the difference. Record it at capture time.
1. Establish authority and destination
Read the active repository's AGENTS.md chain and any linked governance contract.
Determine:
- the owning repository;
- its declared backlog or tracker;
- whether you may write there;
- required labels, project state, or issue template;
- whether it declares a priority label, and its form.
Filing in the active repository is allowed only when its instructions or the user authorize it. Writing to a different repository or external system needs explicit authorization. Never infer permission from common ownership, a nearby checkout, or an old hardcoded roster.
If the repository declares a file backlog, use that file. If it declares GitHub issues, use the workflow below. Do not create a second queue.
2. Promotion bar
Capture when any of these is true:
- another person or session could act on it;
- it reproduces at
file:lineand has a plausible fix shape; - it is user-visible or blocks a consumer.
Do not file speculation, a problem already fixed by the current change, or a duplicate. A local workaround does not remove the need to capture the owning defect.
3. Classify the origin
Every finding carries one of two origin classes, decided by a single falsifiable test — name what broke, or it is a review finding:
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.
- 1mo ago First seen · 197 lines · 56 tokens per session scan A 46fc951c0a9e
submit-feedback is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 1,768 once invoked, about $0.0002 per session on Opus 5.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-28.
Other skills, from other repositories
gsd-quick-batch
Batch several /skill:gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-pause-work
Create context handoff when pausing work mid-phase.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
gait-session-tracking
GAIT session lifecycle management - branch creation, turn recording, audit logging for every NetClaw operation. Use when starting a new NetClaw session, recording a health check or config change, pinning a pre-change baseline, or viewing the audit trail for a troubleshooting session.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.