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 skills add KarmaloopAI/Jiva --skill coordinationgit clone --depth 1 https://github.com/KarmaloopAI/JivaWrote 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/skills/karmaloopai/jiva/coordination)<a href="https://agentmods.dev/skills/karmaloopai/jiva/coordination"><img src="https://agentmods.dev/badge/skills/karmaloopai/jiva/coordination/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/karmaloopai/jiva/coordination"><img src="https://agentmods.dev/badge/skills/karmaloopai/jiva/coordination.svg" alt="Reviewed on agentmods" width="80" 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.00050 | $0.00364 |
| Opus 5.5 | $0.00020 | $0.00146 |
| Sonnet 5.5 | $0.00010 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
team-coordination 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 1mo 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
Team Coordination Skill
Overview
Coordinate complex software engineering tasks by leveraging specialized team member personas.
Workflow
- Analyze Requirements: Break down user request into specialized work streams
- Delegate to Specialist: Spawn sub-agents with appropriate personas:
developer: For implementation workcode-reviewer: For code review and security analysistester: For test creation and validation
- Coordinate Work: Ensure specialists have proper context and task clarity
- Integrate Results: Combine outputs from different specialists into final deliverable
- Report Status: Provide comprehensive summary to user
Available Team Members
- developer: Implements features, fixes bugs, writes production code
- code-reviewer: Reviews code for bugs, security issues, performance, style
- tester: Creates unit tests, integration tests, validates functionality
Example Usage
When user says: "Build a user authentication system"
- Spawn
developerto implement auth logic - Spawn
code-reviewerto review security - Spawn
testerto write comprehensive tests - Integrate all their work into final deliverable
Best Practices
- Give each specialist a clear, focused task
- Provide sufficient context from user's original request
- Don't spawn agents for trivial work you can do directly
- Review specialist outputs before final delivery
- Synthesize findings across specialists when multiple perspectives are valuable
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.
- 1mo ago First seen · 45 lines · 50 tokens per session scan A ccc158557d56
team-coordination is a skill published in the GitHub repository KarmaloopAI/Jiva (35 stars, last pushed 8d ago), licensed MIT. It adds 50 tokens to every session and 364 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
aomi-transact
Build natural-language crypto/DeFi agents and EVM MCP plugins (Claude Code, Cursor, Codex, Gemini). Aomi turns prompts into wallet-signed txs on Ethereum, Base, Arbitrum, Optimism, Polygon, Linea — non-custodial, fork-simulated. 40+ apps: Uniswap, Aave, Lido, Morpho, GMX, Hyperliquid, Polymarket.
clinicaltrials-database
Query ClinicalTrials.gov via API v2. Search trials by condition, drug, location, status, or phase. Retrieve trial details by NCT ID, export data, for clinical research and patient matching.
esm
Comprehensive toolkit for protein language models including ESM3 (generative multimodal protein design across sequence, structure, and function) and ESM C (efficient protein embeddings and representations). Use this skill when working with protein sequences, structures, or function prediction; designing novel…
openalex-database
Query and analyze scholarly literature using the OpenAlex database. This skill should be used when searching for academic papers, analyzing research trends, finding works by authors or institutions, tracking citations, discovering open access publications, or conducting bibliometric analysis across 240M+ scholarly…
glycoengineering
Analyze and engineer protein glycosylation. Scan sequences for N-glycosylation sequons (N-X-S/T), predict O-glycosylation hotspots, and access curated glycoengineering tools (NetOGlyc, GlycoShield, GlycoWorkbench). For glycoprotein engineering, therapeutic antibody optimization, and vaccine design.
pysam
Genomic file toolkit. Read/write SAM/BAM/CRAM alignments, VCF/BCF variants, FASTA/FASTQ sequences, extract regions, calculate coverage, for NGS data processing pipelines.