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/xt765/langchain-chinese-comment/test_responses_specgit clone --depth 1 https://github.com/xt765/LangChain-Chinese-CommentWrote 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/agents/xt765/langchain-chinese-comment/test_responses_spec)<a href="https://agentmods.dev/agents/xt765/langchain-chinese-comment/test_responses_spec"><img src="https://agentmods.dev/badge/agents/xt765/langchain-chinese-comment/test_responses_spec.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.00000 | $0.00108 |
| Opus 5 | $0.00000 | $0.00054 |
| Sonnet 5 | $0.00000 | $0.00022 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
test_responses_spec 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 5d 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.
This is a copy
89% identical to test_responses — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
libs\langchain_v1\tests\unit_tests\agents\test_responses_spec.py
此文档是 libs\langchain_v1\tests\unit_tests\agents\test_responses_spec.py 的中文注释文档占位符。
功能描述
待补充。该模块主要负责 LangChain 的相关功能实现。
参数说明
待补充。
返回值解释
待补充。
使用示例
待补充。
注意事项
待补充。
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.
- 5d ago First seen · 19 lines · 0 tokens per session scan A 541dbf833645
test_responses_spec is an agent published in the GitHub repository xt765/LangChain-Chinese-Comment (20 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 108 tokens. A static security scan graded it A with 0 findings. It is 89% identical to test_responses, differing in 4 lines, and is treated as a copy.
Other agents, from other repositories
test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
frontend-tester
Frontend testing expert for comprehensive test coverage using Vitest, Playwright, and accessibility testing.
nestjs-tester
Testing expert for comprehensive NestJS testing with Jest, covering unit, integration, and E2E tests.
tanstack-tester
Testing expert for TanStack React applications covering unit, integration, and component tests with Vitest, Testing Library, and MSW. Use for writing tests, test architecture, and coverage improvement.
hono-tester
Testing specialist for Hono applications using Bun test and Vitest, covering unit tests, integration tests, and API tests.
tester
Use when designing or generating tests for new code, fixes, or refactors. Dispatched primarily by the test-first skill. Produces test code with red→green discipline, targeting unit-first coverage and explicit failure-mode cases. Pastes runner output as evidence. Context: A new endpoint is being added. user: "Add tests…