Borrowing it
Nothing to install: this file belongs to pppop00/Equity-Research-Company. 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/pppop00/Equity-Research-Company/main/.claude/commands/log-incident.mdgit clone --depth 1 https://github.com/pppop00/Equity-Research-CompanyWrote 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/pppop00/equity-research-company/log-incident)<a href="https://agentmods.dev/commands/pppop00/equity-research-company/log-incident"><img src="https://agentmods.dev/badge/commands/pppop00/equity-research-company/log-incident/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/pppop00/equity-research-company/log-incident"><img src="https://agentmods.dev/badge/commands/pppop00/equity-research-company/log-incident.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.00044 | $0.00834 |
| Opus 5 | $0.00022 | $0.00417 |
| Sonnet 5 | $0.00009 | $0.00167 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
log-incident 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 12d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/log-incident
The user just observed a failure in the most recent run and wants to add a permanent rule to INCIDENTS.md so it cannot recur. This command implements the Curate beat of the Anamnesis Pattern (see references/anamnesis_pattern.md).
What you should do
-
Read the user's
$ARGUMENTS— a short description of what went wrong. -
Pick the latest workspace run — the most recently modified directory under
workspace/{Company}_{Date}/. If none exists, ask the user to point you at the run dir. -
Run the collector to gather a structured digest of that run:
python3 tools/io/log_incident.py --collect --workspace workspace/<latest_run>/ --description "$ARGUMENTS"This prints a JSON digest of the run's validator outputs, structure-conformance, red-team outputs (if present), and the resolved P0 gate values. It does not write to
INCIDENTS.md. -
Read
INCIDENTS.mdto see the existing entry format and the next availableI-NNNid. -
Draft a candidate entry matching the existing format (Phase, What happened, Root cause, Rule (load-bearing), Detection, Related contract). Use concrete paths and values from the digest, not generic prose.
-
Show the candidate entry to the user as a proposed
INCIDENTS.mdappend — do not write it yet. -
Wait for explicit user confirmation. Acceptable confirmations:
yes,confirm,append,ok 写入,OK. Anything else (including silence) means do not append. -
On confirmation, append the entry to
INCIDENTS.md(do not rewrite or reorder existing entries; append-only). Print the path and the appended id back to the user.
Hard rules
- Append only. Never delete, reorder, or rewrite existing
INCIDENTS.mdentries. If a past entry is now incorrect, supersede it with a new entry that links back viaRelated contract:. - Human gate is non-negotiable. Do not append without an explicit user confirmation. Auto-mode does not override this.
- No PII. If the digest contains the user's email (e.g. surfaced from a
User-Agentstring indata_sourcefields), strip it before quoting in the entry. - Specific, not generic. Cite the actual run dir path, the actual workspace JSON paths, the actual values that were wrong. Generic entries don't earn a permanent slot in the system prompt.
- One rule per entry. If the user describes two distinct failures, draft two entries and confirm separately.
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.
- 12d ago First seen · 44 lines · 44 tokens per session scan A 0432f70a2aaa
log-incident is a command published in the GitHub repository pppop00/Equity-Research-Company (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 834 once invoked, about $0.0002 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
research
Professional equity research analysis with institutional-grade formatting.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.