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/vedanta/the-system/integration-engineergit clone --depth 1 https://github.com/vedanta/the-systemWhat 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.00029 | $0.09108 |
| Opus 5 | $0.00015 | $0.04554 |
| Sonnet 5 | $0.00006 | $0.01822 |
| Haiku 4.5 | $0.00003 | $0.00911 |
Grade B, and why
integration-engineer scanned grade B with 2 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 2d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -X POST http://localhost:8000/api/test -d '{"test": true}' \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -f http://localhost:3000/health || echo "Frontend not responding" The source is not reproduced here
Licensed LGPL-3.0
The repository is licensed LGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 2d ago First seen · 1,423 lines · 29 tokens per session scan B f07011023c77
integration-engineer is an agent published in the GitHub repository vedanta/the-system (9 stars, last pushed 6mo ago), licensed LGPL-3.0. It adds 29 tokens to every session and 9,108 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
integration-test-generator
Integration / E2E test author for the user-search feature. Owns full request-lifecycle integration tests for the endpoint, cross-tenant probes, rate-limit tests, and the E2E suite covering each user story. Triggers - "write integration tests for task.
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
delivery-validator
Runtime delivery verification agent. Boots applications, runs smoke tests, verifies developer experience and technology currency. Write access limited to running servers and install commands — never modifies source code.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
devops-infrastructure
Expert in CI/CD, Docker, Kubernetes, cloud infrastructure, and deployment automation.
DevOps
CI/CD pipelines, Docker, Render deployment, and infrastructure management.