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/tesslateai/opensail/claudegit clone --depth 1 https://github.com/TesslateAI/OpenSailWrote 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/tesslateai/opensail/claude)<a href="https://agentmods.dev/agents/tesslateai/opensail/claude"><img src="https://agentmods.dev/badge/agents/tesslateai/opensail/claude.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.00340 |
| Opus 5 | $0.00000 | $0.00170 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
CLAUDE 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 3d 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
tests/agents
Purpose
Unit coverage for the multi-agent orchestration skeleton:
- ticket allocator (
app/services/agent_tickets.py) - budget interceptor (
app/services/agent_budget.py) - approval gate (
app/services/agent_approval.py)
Each test migrates a throwaway SQLite file to head so the schema
matches what ships in production, then exercises the services via a real
AsyncSession.
Key files
conftest.py—sqlite_url,async_session,session_factoryfixtures + amake_project_idhelper. SQLite FKs are off by default, which lets tests insertagent_tasksrows without seeding the fullprojects/usersgraph.test_ticket_allocator.py— ref_id monotonicity + concurrent checkout disjointness (10 workers over 10 queued tickets).test_budget.py— unlimited fallback, exhaustion blocking, agent-wide fallback, safe-degrade contract.test_approval.py— gated tool raisesApprovalRequiredand flips status; approve flips back toqueued.
Related contexts
orchestrator/app/services/agent_tickets.pyorchestrator/app/services/agent_budget.pyorchestrator/app/services/agent_approval.pytests/migrations/test_0050_orchestration.py— schema-level checks.
When to load
Load when touching anything in the orchestration skeleton (ticket lifecycle, budget math, approval gating) or when extending the allocator to wire into the worker claim path.
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.
- 3d ago First seen · 36 lines · 0 tokens per session scan A 39597c839073
CLAUDE is an agent published in the GitHub repository TesslateAI/OpenSail (636 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 340 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
tdd-guide
Red-Green-Refactor TDD 사이클 강제. 테스트 먼저 작성 → 최소 코드 구현 → 리팩토링. 커버리지 80%+ 엣지 케이스 분석 포함. Use proactively when 새 기능 구현, 버그 수정, 리팩토링을 시작할 때 — 특히 "TDD로", "테스트 먼저", "테스트 작성"이 포함된 요청. 빌드 에러 수정은 build-error-resolver, E2E는 e2e-runner 사용.
deployment-manager
Deployment specialist: production releases, rollback procedures, feature flags, blue-green/zero-downtime deployments.
tester
Test writing and execution. Runs tests, analyzes coverage, writes missing tests. DELEGATE when user asks: "Write tests for X" / "Add test coverage" / "Test this component" "Run the tests" / "Check if tests pass" / "Run E2E tests" "What's the test coverage?" / "Find untested code" After implementation to verify…
TOOL_PARSE_CORPUS
The behavioral corpus for the text tool-call parser, migrated from 4900 lines of Rust unit tests into executable conformance fixtures for the harn#5142 parse re-platform. Every baseline was generated from the observed stdout of the built binary, never from reasoning and never from the Rust assertions, so the corpus…
test-engineer
Test creation, coverage analysis, and quality assurance specialist with semantic code understanding.
qa-tester
Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.