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/qwize-br/wize-development-kitWrote 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/qwize-br/wize-development-kit/wize-refresh-knowledge)<a href="https://agentmods.dev/commands/qwize-br/wize-development-kit/wize-refresh-knowledge"><img src="https://agentmods.dev/badge/commands/qwize-br/wize-development-kit/wize-refresh-knowledge.svg" alt="Measured on agentmods" 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.00006 | $0.01398 |
| Opus 5 | $0.00003 | $0.00699 |
| Sonnet 5 | $0.00001 | $0.00280 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
wize-refresh-knowledge 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 4d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 4d ago First seen · 127 lines · 6 tokens per session scan A 6471858382db
wize-refresh-knowledge is a command published in the GitHub repository qwize-br/wize-development-kit (13 stars, last pushed 4d ago), with no licence file. It adds 6 tokens to every session and 1,398 once invoked, about $0.0000 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 commands, from other repositories
checkpoint
Export, refresh, verify, or import a comprehensive cross-topic Project Knowledge Checkpoint for a repository, with privacy checks.
audit
Audit .flow/memory/ entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry.
cache-warm
Pre-calentar caché con contexto probable basado en hora y rol.
finish-work
A project wrap-up command for the auto-embedded framework, which supports structured embedded-software development. It runs automated checks, guides a three-part review, records reusable lessons and session notes, and archives the finished task.
handoff
Create a handoff document for seamless session continuity.
continuar
Recuperar sesión previa y generar reporte de puesta al día.