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.
git clone --depth 1 https://github.com/dannyhoang249-hub/pm-vietnamese-skillWrote 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/dannyhoang249-hub/pm-vietnamese-skill/analyze-feedback)<a href="https://agentmods.dev/commands/dannyhoang249-hub/pm-vietnamese-skill/analyze-feedback"><img src="https://agentmods.dev/badge/commands/dannyhoang249-hub/pm-vietnamese-skill/analyze-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/commands/dannyhoang249-hub/pm-vietnamese-skill/analyze-feedback"><img src="https://agentmods.dev/badge/commands/dannyhoang249-hub/pm-vietnamese-skill/analyze-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.00027 | $0.00249 |
| Opus 5 | $0.00014 | $0.00125 |
| Sonnet 5 | $0.00005 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
analyze-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 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.
What it actually says
/analyze-feedback — Phân tích phản hồi
Ngôn ngữ | Language: Match the requester’s language. When asked for bilingual output, retain source quotes in their original language and translate only when useful.
- Nêu nguồn, thời gian, số lượng mẫu, phân khúc và giới hạn dữ liệu nếu biết.
- Nhóm feedback theo nhu cầu/pain/outcome thay vì chỉ sentiment; giữ trích dẫn nguyên văn ngắn khi người dùng cung cấp.
- Phân biệt tần suất, mức độ nghiêm trọng, bằng chứng về nguyên nhân và yêu cầu giải pháp. Không suy ra prevalence từ vài ví dụ.
- Xác định insight có thể hành động, counter-signal và những điều dữ liệu chưa thể kết luận.
- Đề xuất bước kế tiếp: nghiên cứu sâu hơn, instrument, thay đổi nhỏ, hoặc đưa vào discovery/prioritization.
- Trả về Feedback synthesis theo
references/templates-vi.md.
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 · 16 lines · 27 tokens per session scan A b60614e577d1
analyze-feedback is a command published in the GitHub repository dannyhoang249-hub/pm-vietnamese-skill (1 stars, last pushed 22d ago), licensed MIT. It adds 27 tokens to every session and 249 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-08-31.
Other commands, from other repositories
plan
Sequence from done, not from the ticket.
log
Show recent git history with summary.
brain-fog-mode
Alias for foggy mode using the user's brain-fog wording.
resolve-review.body
$ARGUMENTS.
persona
Build an evidence-based persona.
checklist
Generate a custom checklist for the current feature based on user requirements.