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 jqaisystems/jqai-ai-skills --skill implement-client-feedbackgit clone --depth 1 https://github.com/jqaisystems/jqai-ai-skillsWrote 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/jqaisystems/jqai-ai-skills/implement-client-feedback)<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/implement-client-feedback"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/implement-client-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/jqaisystems/jqai-ai-skills/implement-client-feedback"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/implement-client-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.00065 | $0.00593 |
| Opus 5.5 | $0.00026 | $0.00237 |
| Sonnet 5.5 | $0.00013 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
implement-client-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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Client Feedback
Turn client language into a controlled implementation contract, apply the authorized changes, and verify the result against the feedback source.
1. Establish the authoritative feedback set
- Confirm the project root, current artifact or version, feedback source, and requested outcome.
- Read the latest approved brief, feedback, current implementation, and relevant handoff material before changing files.
- Treat the latest explicit decision as authoritative when it overrides earlier direction.
- Preserve literal replacement text, names, exclusions, filenames, and approved claims.
2. Build the feedback matrix
- Use assets/feedback-implementation-brief.md.
- Classify every item as
change,keep,remove,exclude,question, orfuture. - Record the literal instruction, minimal interpretation, target, acceptance evidence, and status.
- Keep rejected concepts in a prominent exclusion list so older files or templates cannot reintroduce them.
- Separate client requests from optional internal improvements.
3. Resolve only material ambiguity
- Inspect the current artifact to resolve locations, nearby patterns, and implementation details.
- Record small reversible assumptions that cannot change the intended outcome.
- Ask before choosing a visual direction, changing approved scope, removing a public route, altering rights or deliverables, or contradicting literal feedback.
- Do not turn a focused revision into a redesign.
4. Implement with controlled scope
- Follow the project's existing architecture, versioning, and file conventions.
- Start from the latest approved foundation.
- Preserve approved elements and unrelated user-owned changes.
- Apply only confirmed changes and keep excluded items absent.
- Use the appropriate project tools for code, copy, images, documents, or website work.
- Do not deploy, publish, upload, send, or change external permissions unless the user explicitly authorizes that separate action.
What ships with it
2 files 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.
- 1mo ago First seen · 52 lines · 65 tokens per session scan A defb8b6dbcf0
implement-client-feedback is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 65 tokens to every session and 593 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
ledger-tasks-yylo
Retrieve any YYLO Ledger Record by ID, discover PDRs and artifacts, and manage tasks and dependencies. Use for unknown record types, universal get/search, task operations, and source-of-truth boundaries.
grill-me
Grill the user about a requirement, decision, or idea before implementation, then produce an actionable planning report without writing code. Use when the user wants to clarify requirements, stress-test an idea, compare approaches, or plan before coding.
wiki-yylo
Use YYLO Ledger wiki Records as durable project knowledge. Search before creating, classify information correctly, and make revision-safe Markdown updates without editing Ledger storage directly.
plan-ledger-tasks-yylo
Create a concise Product Development Requirement and one or more implementation-sized YYLO Ledger tasks when the user explicitly asks to plan or register work.
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…