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 asaotomo/DeepSentry --skill forensicsgit clone --depth 1 https://github.com/asaotomo/DeepSentryWrote 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/asaotomo/deepsentry/forensics)<a href="https://agentmods.dev/skills/asaotomo/deepsentry/forensics"><img src="https://agentmods.dev/badge/skills/asaotomo/deepsentry/forensics/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/asaotomo/deepsentry/forensics"><img src="https://agentmods.dev/badge/skills/asaotomo/deepsentry/forensics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00461 |
| Opus 5.5 | $0.00013 | $0.00184 |
| Sonnet 5.5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
forensics 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 1mo 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
文件取证 Skill
何时使用
- 分析可疑二进制、Webshell、恶意样本
- 读取
.gz压缩日志（auth.log、nginx access.log 等） - 目标系统无
file、strings、zcat、gunzip命令
工具选用
| 场景 | 工具 | 示例 |
|---|---|---|
| 文件是什么类型 | file_ident |
{"tool_name":"file_ident","tool_args":{"path":"/tmp/suspicious"}} |
| 提取硬编码字符串/IP/URL | file_strings |
{"tool_name":"file_strings","tool_args":{"path":"/var/www/x.php","pattern":"eval|base64"}} |
| 读 gzip 日志 | read_gzip |
{"tool_name":"read_gzip","tool_args":{"path":"/var/log/auth.log.1.gz","lines":"100"}} |
| 不确定是否 gzip | read_log |
{"tool_name":"read_log","tool_args":{"path":"/var/log/syslog","pattern":"Failed"}} |
| 文件哈希 | file_hash |
{"tool_name":"file_hash","tool_args":{"path":"/bin/busybox"}} |
推荐流程
file_ident— 确认文件类型（ELF/PHP/GZIP/文本）- 若为 gzip 日志 →
read_log或read_gzip+ pattern 过滤 - 若为二进制/可疑脚本 →
file_strings+ pattern file_hash— 留存 IOC
限制
- 单文件读取上限 5MB（压缩），解压上限 20MB
- strings 扫描上限 2MB
- 禁止读取 config.yaml / reports/ 等受保护路径
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.
- 1mo ago First seen · 37 lines · 32 tokens per session scan A 867c28a214e3
forensics is a skill published in the GitHub repository asaotomo/DeepSentry (38 stars, last pushed 3d ago), licensed Apache-2.0. It adds 32 tokens to every session and 461 once invoked, about $0.0001 per session on Opus 5.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
go-expert
Expert-level Go development with Go 1.22+ features, concurrency, standard library, and production-grade best practices. Use when the user mentions concurrency, microservices, or backend, or when the task involves idiomatic Go, goroutines and channels, context-based cancellation, or writing an HTTP server.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
golang-patterns
Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.
stack-trace-go-probe
Internal helper for meta-stack-trace-investigator. Use when a Go panic or stack trace needs Go-specific nil/error checks, go test reproducer guidance, and patch targets.
ax-go-gen
Use when writing Go code with github.com/ax-llm/ax/packages/go for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.
ax-go-agent
Use when writing Go code with github.com/ax-llm/ax/packages/go for agents, child delegation, tools, MCP, citations, persistent playbook learning, stage instructions, runtime state, final typed responses, and direct-respond executor skipping.