Borrowing it
Nothing to install: this file belongs to nirelbaz/promptpit. 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/nirelbaz/promptpit/main/.claude/commands/refresh-knowledge.mdgit clone --depth 1 https://github.com/nirelbaz/promptpitWrote 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/nirelbaz/promptpit/refresh-knowledge)<a href="https://agentmods.dev/commands/nirelbaz/promptpit/refresh-knowledge"><img src="https://agentmods.dev/badge/commands/nirelbaz/promptpit/refresh-knowledge/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/nirelbaz/promptpit/refresh-knowledge"><img src="https://agentmods.dev/badge/commands/nirelbaz/promptpit/refresh-knowledge.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.00000 | $0.00501 |
| Opus 5.5 | $0.00000 | $0.00200 |
| Sonnet 5.5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
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 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.
Read the AI Stack Expert agent definition at .claude/agents/ai-stack-expert.md to understand your role, expertise, and methodology. Then execute the following refresh workflow.
Scope
$ARGUMENTS
If a specific tool name was provided above (e.g., "cursor"), refresh only that tool's knowledge file. Otherwise, refresh all tools in docs/knowledge/.
Workflow
Step 0: Inventory
Read all files in docs/knowledge/ and sort by last-verified date (oldest first). This is your refresh priority order.
Step 1: Per-Tool Refresh
For each tool (or the specified tool):
- Read current knowledge file from
docs/knowledge/<tool>.md - Check freshness — if
last-verifiedis less than 7 days old and no specific tool was requested, skip it - Research current state using WebSearch and WebFetch:
- Search the tool's official documentation (URLs in the
doc-urlsfrontmatter) - Check for recent changelog entries, blog posts, or release notes
- Search for configuration documentation: file paths, formats, supported features
- Search for MCP server support, agent support, rules/instructions support
- Search for any cross-tool reading behavior (does it read AGENTS.md, .mcp.json, etc.?)
- Search the tool's official documentation (URLs in the
- Update the knowledge file with verified findings:
- Fill in or update all sections: Configuration, Cross-Tool Reading, Behavior, Ecosystem, Edge Cases
- For tools with
status: adapter-exists, update the Promptpit Gaps section by comparing what the tool supports vs what the adapter implements - Update
last-verifiedto today's date - Add or update
doc-urlswith any new documentation sources discovered
- Do NOT modify any source code — this command only updates knowledge files
Step 2: Summary
After refreshing, print a summary:
## Knowledge Refresh Summary — YYYY-MM-DD
### Refreshed
- <tool>: <what changed or was verified>
### Skipped (recently verified)
- <tool>: last verified YYYY-MM-DD
### Breaking Changes Detected
- <any changes that affect promptpit adapters>
### New Tools Discovered
- <any new AI coding tools worth tracking>
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 · 0 tokens per session scan A 2b4cdaf49178
refresh-knowledge is a command published in the GitHub repository nirelbaz/promptpit (6 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 501 tokens. 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
revise-claude-md
Update FUXI.md with learnings from this session.
remember
Save the user's input into Tau Git Memory now.
tree
Show the Tau Git Memory tree as a visual schema.
recall
Search Tau Git Memory now for.
status
Run Tau Git Memory status now.
ask-about-me
Ask a question about the user's personal profile via the mcp-me MCP server.