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/mcb-smart-boy/nixos-config/debugnpx skills add MCB-SMART-BOY/nixos-config --skill debuggit clone --depth 1 https://github.com/MCB-SMART-BOY/nixos-configWrote 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/mcb-smart-boy/nixos-config/debug)<a href="https://agentmods.dev/skills/mcb-smart-boy/nixos-config/debug"><img src="https://agentmods.dev/badge/skills/mcb-smart-boy/nixos-config/debug.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.00042 | $0.00746 |
| Opus 5 | $0.00021 | $0.00373 |
| Sonnet 5 | $0.00008 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
debug 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.
What it actually says
Debug
错误分类
| 特征 | 类型 | 查什么 |
|---|---|---|
error: undefined variable |
未定义变量 | 拼写、with 污染 |
error: attribute 'xxx' missing |
属性缺失 | nixpkgs API 变更、包名错误 |
error: The option 'xxx' is used but not defined |
选项未声明 | 去 modules/options.nix 声明 |
error: infinite recursion |
无限递归 | 自引用配置 |
error: value is X while a Y was expected |
类型不匹配 | 选项类型声明 |
error: A definition for option 'xxx' is not of type '...' |
选项类型错误 | 检查赋值类型 |
诊断流程
nix flake check 2>&1 # eval 阶段
nixos-rebuild build --flake /etc/nixos#<machine> 2>&1 | tee build.log # 构建阶段
nix log /nix/store/<hash>-<name>.drv # 构建日志
nix flake check --show-trace 2>&1 | head -100 # 完整 trace
常见陷阱
| 症状 | 根因 | 修复 |
|---|---|---|
No such file or directory (新 .nix 文件) |
没 git add |
git add <文件> |
mcb.xxx is used but not defined |
在功能模块中声明选项 | 移到 modules/options.nix |
undefined variable |
with lib; 污染 |
显式 lib.xxx |
| 列表被覆盖 | 直接赋值 = [pkg] |
用 lib.mkAfter |
greetd 问题
journalctl -u greetd -b --no-pager | tail -80 # 查看 greetd 日志
| 日志特征 | 原因 | 修复 |
|---|---|---|
| greeter 不断重启 | greeter 崩溃 → greetd restart loop | 检查 greeter 命令是否正确；agreety 是最可靠的选项 |
unrecognized option '-s' / '-d' / '-m' |
cage >=0.2 废弃旧参数 | 清空 cageArgs，移除 greetd command 中的对应参数 |
Failed to initialize GTK / 白屏 |
Mesa 回归（regreet 等图形 greeter） | 切换到 agreety（无 GTK/Mesa 依赖），或加 GSK_RENDERER=ngl |
| cage 找不到 GPU/DRM | 内核模块未加载 | lsmod | grep i915；检查 hardware-gpu.nix |
运行时
systemctl --failed # 失败服务
journalctl -u <service> -b # 服务日志
loginctl list-sessions # 桌面会话
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 · 57 lines · 42 tokens per session scan A d5a15f680636
debug is a skill published in the GitHub repository MCB-SMART-BOY/nixos-config (10 stars, last pushed 8d ago), licensed Apache-2.0. It adds 42 tokens to every session and 746 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…