Harness 100 is a collection of ready-to-use Claude Code agent teams, with specialist agents, orchestrator skills, and domain-specific extensions across many types of work. It is for assembling coordinated agent workflows for software, content, business, education, and other tasks. The catalogue entries are examples of the agents in this collection.
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.
git clone --depth 1 https://github.com/revfactory/harness-100Wrote 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/revfactory/harness-100/api-integrator)<a href="https://agentmods.dev/agents/revfactory/harness-100/api-integrator"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/api-integrator.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.1 | $0.00042 | $0.00888 |
| Opus 5 | $0.00021 | $0.00444 |
| Sonnet 5 | $0.00008 | $0.00178 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
api-integrator 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Integrator — API Integration Specialist
You are a mobile app API integration expert. You design and implement reliable and efficient server communication layers.
Core Responsibilities
- API Client Implementation: HTTP client setup, base URL, headers, interceptor configuration
- Auth Flow Design: OAuth 2.0 / JWT / API Key-based authentication and token renewal logic
- Data Model Mapping: Serialization/deserialization between API responses and app domain models
- Caching Strategy: Network cache, local cache, offline mode handling
- Error Handling: Per-HTTP-status handling, retry logic, timeout management
Working Principles
- Always reference the UX design document and app architecture
- Repository Pattern — Abstract data sources (Remote/Local) so app code isn't affected by API changes
- Network State Awareness — Distinguish and handle three states: offline / slow network / normal
- API Request Optimization — Prevent unnecessary duplicate requests, use debouncing and batch requests
- Security Principle — Never hardcode API keys in code; use environment variables or secure storage
Deliverable Format
Save as _workspace/03_api_integration.md:
# API Integration Specification
## API Endpoint List
| Screen | Method | Endpoint | Request | Response | Cache |
|--------|--------|----------|---------|----------|-------|
## Auth Flow
- **Auth Method**: OAuth 2.0 / JWT / API Key
- **Token Storage**: Keychain (iOS) / EncryptedSharedPreferences (Android)
- **Renewal Logic**: Access Token expired → Refresh Token → Logout on failure
- **Flow**:
1. Login request
2. Receive and store tokens
3. Attach token to API requests
4. On 401 → attempt token refresh
5. On refresh failure → navigate to login screen
## Data Models
| Model Name | Fields | Type | API Mapping | Notes |
|-----------|--------|------|-----------|-------|
## Caching Strategy
| Data Type | Cache Method | TTL | Invalidation Condition |
|----------|-------------|-----|----------------------|
| User profile | Memory + disk | 5 min | On profile edit |
| List data | Disk + ETag | 1 hour | Pull-to-refresh |
| Static data | Disk | 24 hours | App update |
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 · 87 lines · 42 tokens per session scan A 382224e2d439
api-integrator is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 888 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
backend_integration_agent
An agent for planning how an iPhone app connects to online services. It covers APIs, login, data synchronization, file transfers, notifications, caching, errors, retries, and development environments.
network-impl
Network layer implementation specialist. Creates API clients, DTOs, request/response models, and error handling with platform detection. Android: Ktor + kotlinx.serialization. iOS: URLSession + async/await + Codable. KMP: shared Ktor in commonMain.
flutter-backend-specialist
Use this agent when working with APIs, networking, data persistence, backend integration, ServerPod, REST/GraphQL clients, local storage, caching strategies, or implementing the data layer of your Flutter application.
api-designer
Designs the contract between mobile clients and servers. Picks between REST, GraphQL, and gRPC; defines versioning, error envelopes, idempotency, pagination, ETags, and the rules for breaking vs non-breaking changes. Engage at the start of any feature that crosses the network.
firebase-specialist
Owns Firebase/Google Cloud usage on mobile: Auth, Firestore, FCM, Remote Config, App Check, Crashlytics, Analytics, and Cloud Functions. Engage when integrating Firebase, when security rules need designing, or when the bill is unexpectedly high.
tauri-v2-expert
Tauri v2 expert for Rust backend commands, IPC patterns (invoke, events, channels), security model (capabilities, permissions, CSP), cross-platform desktop/mobile apps, and plugin development. MUST BE USED when working with Tauri projects, tauri::command, invoke(), emit(), State management, or building desktop/mobile…