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/DyanGalih/spec-kit-memory-hubWrote 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/dyangalih/spec-kit-memory-hub/speckit.memory-md.log-finding)<a href="https://agentmods.dev/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.log-finding"><img src="https://agentmods.dev/badge/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.log-finding/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/dyangalih/spec-kit-memory-hub/speckit.memory-md.log-finding"><img src="https://agentmods.dev/badge/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.log-finding.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.00297 |
| Opus 5 | $0.00014 | $0.00148 |
| Sonnet 5 | $0.00005 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
speckit.memory-md.log-finding 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 9d 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
Log Finding
Turn a high-signal audit finding into a tracker-ready follow-up.
Use this when:
- an audit finding should be tracked outside memory
- the team wants a bug, cleanup task, or follow-up item in GitHub Issues, GitLab Issues, Jira, or another tracker
- the finding is worth action but not worth storing as durable memory on its own
Before creating anything, identify:
- target platform
- target project, repository, or board
- issue type or category
- priority or severity
- whether the item is a bug, cleanup task, or investigation
For each logged finding:
- preserve the evidence
- keep the title short and actionable
- include a concise summary of the problem
- include the memory or diff evidence that supports it
- include the recommended next action
- include labels or fields that match the destination platform
If a direct write integration exists in the current environment, create the issue there. If no write integration exists, produce a tracker-ready draft that can be pasted into the chosen platform.
Do not rewrite memory here. Do not create noisy or speculative follow-up items.
If the finding is approved as durable memory after tracking, call speckit_memory_refresh_cache(scope="memory") when the optimizer and MCP server are enabled and available.
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.
- 9d ago First seen · 39 lines · 27 tokens per session scan A b1e9d8e55f9f
speckit.memory-md.log-finding is a command published in the GitHub repository DyanGalih/spec-kit-memory-hub (15 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 297 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-30.
Other commands, from other repositories
linear-drain
Create the queued Linear projects and issues that shell scripts captured offline.
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.
sddp-analyze
Command description: Audit spec, plan, and tasks for consistency and quality. Argument hint: [optional: analysis focus or remediation request] Command category: feature-delivery Prerequisites: spec, plan, tasks.
sddp-prd
Command description: Create or refine the canonical product document. Argument hint: [rough product idea, users, domain, or market opportunity] Command category: project-bootstrap Prerequisites: none.
today
Create a morning heartbeat from repository state and update the local heartbeat log.
sddp-amend
Command description: Propagate a bootstrap change across canonical project artifacts and the project plan. Argument hint: [project-level change to propagate across bootstrap artifacts] Command category: project-bootstrap Prerequisites: project-instructions, product-document, technical-context, project-plan.