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 skills add FuRongJun-1999/dsh-memory --skill compiler-11897630git clone --depth 1 https://github.com/FuRongJun-1999/dsh-memoryWrote 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/furongjun-1999/dsh-memory/compiler-11897630)<a href="https://agentmods.dev/skills/furongjun-1999/dsh-memory/compiler-11897630"><img src="https://agentmods.dev/badge/skills/furongjun-1999/dsh-memory/compiler-11897630/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/skills/furongjun-1999/dsh-memory/compiler-11897630"><img src="https://agentmods.dev/badge/skills/furongjun-1999/dsh-memory/compiler-11897630.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.00083 | $0.00410 |
| Opus 5 | $0.00042 | $0.00205 |
| Sonnet 5 | $0.00017 | $0.00082 |
| Haiku 4.5 | $0.00008 | $0.00041 |
Grade A, and why
compiler-11897630 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 today.
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
调试-覆盖率（compiler-11897630）
When to use
任务「覆盖率」；对照：C4 覆盖率——指令覆盖百分比（测试充分性）。
克制条款（不适用条件）
total 为空/非法时；op 非 {mark, report} 时
How to execute
按 op 分派；顺序调用
Verification
- 单元样例 3 条（cases 断言）
- 物理基底：按 calibration 对照（编译/运行/断言裁决）
References
- 单元库：compiler_code_units.py「调试-覆盖率」
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.
- today First seen · 46 lines · 83 tokens per session scan A 99a398b9443f
compiler-11897630 is a skill published in the GitHub repository FuRongJun-1999/dsh-memory (159 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 410 once invoked, about $0.0004 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-11.
Other skills, from other repositories
safe-patch-authoring
Use only after a root cause is evidenced to create the smallest patch, focused tests, a dedicated branch and commit, and optionally a pull request under the pullrequestonly policy.
working-effectively-with-legacy-code
Apply Michael Feathers-inspired legacy-code rules when changing hard-to-test code safely with characterization tests, seams, sprout methods, or wrap methods.
refactoring
Apply Martin Fowler-inspired refactoring rules when improving existing code structure while preserving observable behavior.
neqsim-regression-baselines
Regression baseline management for NeqSim. USE WHEN: modifying solver logic, property correlations, or EOS implementations. Ensures changes don't silently degrade accuracy. Covers creating baseline fixtures, writing regression tests, and detecting accuracy drift.
dos-self-improve
Run the DOS self-improvement loop: propose a candidate, verify it in an isolated worktree, measure suite/truth/metric gates, and keep only confirmed gains. Use for recursive improvement; use dos-enforce-tune for policy knobs.
fix-bug
Diagnoses and fixes bugs using a test-first workflow (reproduce, diagnose, fix). Use this skill whenever the user reports a bug, describes unexpected behavior, or asks to investigate or fix a defect. Even if the user says "something's broken", "this isn't working", "fix this bug", or "why does X happen", load this…