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 agentmods add skills/pascalebeier/hitkeep/hitkeep-qanpx skills add PascaleBeier/hitkeep --skill hitkeep-qagit clone --depth 1 https://github.com/PascaleBeier/hitkeepWrote 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/pascalebeier/hitkeep/hitkeep-qa)<a href="https://agentmods.dev/skills/pascalebeier/hitkeep/hitkeep-qa"><img src="https://agentmods.dev/badge/skills/pascalebeier/hitkeep/hitkeep-qa.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 | $0.00057 | $0.00612 |
| Opus 5 | $0.00028 | $0.00306 |
| Sonnet 5 | $0.00011 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
hitkeep-qa 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.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HitKeep QA
Treat AGENTS.md as repository policy and the live hk QA catalog as workflow truth. Never reproduce the gate matrix, commands, tags, or tool versions in this skill or in a contribution plan.
Select
Use hk_qa_plan whenever it is callable. If it is absent or fails, report whether registration, startup, workspace routing, or task reload is blocking MCP and obtain explicit user approval before using an equivalent CLI action. After approval, discover the planning command through ./hk qa --help and request --output json.
- Use
changedwhile iterating. - Use
completebefore declaring contributor work complete; it runs the deepest locally appropriate gates for affected areas. - Use
pronly for exact unchanged CI parity. - Use
fullwhen release risk, cloud-tagged behavior, container behavior, or the request explicitly requires exhaustive validation.
Honor planner escalation. Query hitkeep-dev://catalog/qa or the structured CLI catalog for current profiles and gate definitions rather than guessing or copying commands.
Use hk_run_status to observe the returned run and request bounded cursor-addressed run or gate logs. Use hk_run_cancel only for the intended exact observed active run.
Run and Observe
- Inspect
hk_contextand known run status for equivalent active QA work before starting another. - Persist a source-bound plan with
hk_qa_plan, then pass its requiredplan_idtohk_run_start. Use a structured CLI action with--detach --output jsononly after the MCP blocker has been reported and the user has approved fallback. Keep the returned workspace ID and run ID. - Poll
hk_run_statusrather than restarting a slow run or assuming client disconnect stopped it. - On failure, request the bounded run tail, then a bounded gate-specific view from
hk_run_status. Open the complete local artifact only when that context is insufficient. - Fix the root cause and rerun the smallest relevant selection from the live catalog before rerunning the required profile.
- Let all selected gates finish; one failure must not hide independent results. Cancel only the intended validated run.
What ships with it
1 file 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.
- 4d ago First seen · 37 lines · 57 tokens per session scan A 91ced3a9c4ce
hitkeep-qa is a skill published in the GitHub repository PascaleBeier/hitkeep (85 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 612 once invoked, about $0.0003 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-30.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
drt-analyze
Analyze DRT cluster health for a given time range. Reconstructs the operations timeline, checks CockroachDB metrics (availability, latency, storage, changefeeds, jobs, goroutines, admission control, LSM, KV prober) and logs for anomalies, correlates findings with disruptive operations to distinguish expected…
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
file-crdb-issue
Use when filing, creating, or reporting GitHub issues for CockroachDB. Use when asked to open a bug report, feature request, investigation issue, or performance inquiry. Also use when the user mentions wanting to track a problem, report a regression, or document unexpected behavior in CockroachDB.
engflow-artifacts
Use when downloading test logs, artifacts, or outputs.zip from EngFlow build invocations. Use when investigating CockroachDB CI test failures hosted on mesolite.cluster.engflow.com.