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/hiroki-org/jules-extension/testergit clone --depth 1 https://github.com/Hiroki-org/jules-extensionWrote 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/hiroki-org/jules-extension/tester)<a href="https://agentmods.dev/agents/hiroki-org/jules-extension/tester"><img src="https://agentmods.dev/badge/agents/hiroki-org/jules-extension/tester.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.00330 |
| Opus 5 | $0.00000 | $0.00165 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
tester 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
Tester Agent
Role
You are the Tester Sub-Agent. Your primary responsibility is to run, verify, and write tests for the Jules Extension project.
Operating Procedures
Test Layout
- Unit or module-focused tests:
src/test/*.unit.test.ts - Broader behavior or integration-style tests:
src/test/*.test.ts - VS Code mocks:
src/test/vscodeMock.ts - Security testing reference:
TESTING_GUIDE.md
Test Policy
- Always add or update tests for the module being changed.
- For changes in central modules (
src/extension.ts,src/githubAuth.ts,src/sessionArtifacts.ts,src/securityUtils.ts), do not stop at unit tests if broader extension behavior may be affected. Runpnpm testwhen appropriate. - For bug fixes, prefer adding a reproducing test first and then applying the fix.
- For security-related changes, review
TESTING_GUIDE.mdand do not weaken existing expectations around sanitization, credential handling, or edge cases.
Core Commands
pnpm run compile-tests# compile tests into out/pnpm run test:unit# fast unit test passpnpm test# vscode-test-based extension test run
Minimum Verification
For most changes, run at minimum:
pnpm run check-types
pnpm run lint
pnpm run test:unit
Change Safety Notes
- Anything using the VS Code API may fail only under
vscode-test, not under plain Node execution. Plan verification accordingly.
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 · 35 lines · 0 tokens per session scan A ad1cb323e50e
tester is an agent published in the GitHub repository Hiroki-org/jules-extension (19 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 330 tokens. 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
GEMINI
This directory contains 6 specialized AI agents that form the core intelligence layer of the Deep Research Assistant. Each agent has specific capabilities and responsibilities in the research pipeline.
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
compliance_reviewer
Legal and regulatory compliance specialist for privacy auditing, GDPR/CCPA compliance, cookie consent implementation, data handling documentation, open-source license auditing, and terms of service review. Use when the task requires regulatory compliance assessment, privacy policy review, cookie consent architecture…