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 agents/binghanofuestc/open_agent_team/stacktrace_agentgit clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_teamWhat 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.00017 | $0.00089 |
| Opus 5 | $0.00009 | $0.00044 |
| Sonnet 5 | $0.00003 | $0.00018 |
| Haiku 4.5 | $0.00002 | $0.00009 |
Grade A, and why
stacktrace_agent 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 2d 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
stacktrace_agent
必须使用 skills/log-and-stacktrace-analysis/SKILL.md。
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.
- 2d ago First seen · 16 lines · 17 tokens per session scan A 00adcb8db917
stacktrace_agent is an agent published in the GitHub repository BingHanOfUESTC/open_agent_team (110 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 89 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 agents, from other repositories
claude-codebase-context
Internal Claude subagent for codebase-aware code review — quality patterns, CLAUDE.md compliance, git history analysis, and documentation coverage. Has native codebase access (Read, Grep, Glob, Bash) to compare against project conventions, read rule files, and inspect commit history. Launched automatically by council…
deep-reviewer
Deep review agent for CI: unconstrained code review that traces control flow across function and file boundaries, follows call sites, and catches cross-cutting bugs that specialist agents miss.
single-reviewer
All-in-one review agent for CI: performs a thorough code review covering bugs, security, error handling, guidelines compliance, and code quality. Used by --single mode for cost-effective reviews.
researcher
Documentation and research specialist. Queries Context7 for library docs, searches web for best practices, and returns structured findings. Reusable across planning and development phases. Context: The architect needs library documentation for a design decision. assistant: "I'll launch the researcher agent to look up…
security-reviewer
Security-focused review agent for CI: scans PR diffs for OWASP top 10 vulnerabilities, injection flaws, authentication/authorization issues, exposed secrets, and unsafe data handling.
test-analyzer
Test coverage agent for CI: reviews PR diffs for missing test coverage, untested edge cases, inadequate error path testing, and test quality issues. Focuses on behavioral coverage over line metrics.