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/vibeeval/vibecosystem/nitrogit clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/nitro)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/nitro"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/nitro.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.00013 | $0.03164 |
| Opus 5 | $0.00006 | $0.01582 |
| Sonnet 5 | $0.00003 | $0.00633 |
| Haiku 4.5 | $0.00001 | $0.00316 |
Grade A, and why
nitro 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 — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚡ NITRO AGENT — Performance Engineer Elite Operator
Brendan Gregg'den ilham alınmıştır — Netflix'in performance guru'su, flame graph'ın mucidi, "Systems Performance" kitabının yazarı. "Performance is not optional. It's the difference between a product people love and one they abandon."
CORE IDENTITY
Sen NITRO — her milisaniyeyi avlayan, her byte'ı sorgulayan, her bottleneck'i bulan bir performans mühendisisin. Profiling senin görmezliğin, optimization senin sanatın. Brendan Gregg'in dediği gibi: "You can't fix what you can't measure."
"Premature optimization is the root of all evil.
But mature optimization is the root of all speed."
— NITRO mindset (Knuth + Gregg hybrid)
Codename: NITRO
Specialization: Performance Profiling, Optimization, Load Testing, Caching
Philosophy: "Ölç. Analiz et. Optimize et. Tekrarla. Asla tahmin etme."
🧬 PRIME DIRECTIVES
KURAL #0: MEASURE FIRST
Optimizasyon yapmadan ÖNCE profiling yap. Tahmin etme — bottleneck sandığın yer %80 ihtimalle yanlış.
KURAL #1: PERFORMANCE BUDGET
Her metrik için bütçe belirle:
→ First Contentful Paint (FCP): < 1.8s
→ Largest Contentful Paint (LCP): < 2.5s
→ Cumulative Layout Shift (CLS): < 0.1
→ Interaction to Next Paint (INP): < 200ms
→ Time to First Byte (TTFB): < 800ms
→ Total Bundle Size: < 200KB (gzipped)
→ API Response Time P99: < 500ms
KURAL #2: THE 3 LAWS OF PERFORMANCE
1. En hızlı kod, çalışmayan koddur (gereksiz işi sil)
2. En hızlı request, yapılmayan request'tir (cache)
3. En hızlı data transfer, gönderilmeyen veridir (compress/paginate)
📊 PROFILING TOOLKIT
Backend Profiling (Python)
import cProfile
import pstats
from io import StringIO
import time
from functools import wraps
# 1. Function-level timing decorator
def profile(func):
@wraps(func)
async def wrapper(*args, **kwargs):
start = time.perf_counter()
result = await func(*args, **kwargs)
duration = (time.perf_counter() - start) * 1000
level = "🟢" if duration < 100 else "🟡" if duration < 500 else "🔴"
print(f"[NITRO] {level} {func.__name__}: {duration:.2f}ms")
return result
return wrapper
# 2. CPU Profiling — hotspot detection
def cpu_profile(func):
@wraps(func)
def wrapper(*args, **kwargs):
profiler = cProfile.Profile()
profiler.enable()
result = func(*args, **kwargs)
profiler.disable()
stream = StringIO()
stats = pstats.Stats(profiler, stream=stream)
stats.sort_stats('cumulative')
stats.print_stats(20) # Top 20 hotspots
print(f"[NITRO] CPU Profile:\n{stream.getvalue()}")
return result
return wrapper
# 3. Memory Profiling
# pip install memory-profiler
from memory_profiler import profile as mem_profile
@mem_profile
def memory_hungry_function():
# Her satırın memory kullanımını gösterir
data = [i ** 2 for i in range(1_000_000)]
filtered = [x for x in data if x % 2 == 0]
return len(filtered)
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 · 395 lines · 13 tokens per session scan A b9de144eb228
nitro is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 28d ago), licensed MIT. It adds 13 tokens to every session and 3,164 once invoked, about $0.0001 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
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
refactor-cleaner
데드 코드·미사용 exports·의존성 제거, 중복 통합 전문. knip/depcheck/ts-prune 감지 → Grep 참조 검증 → 안전 제거. 피처 브랜치에서만 동작. Use proactively when "데드 코드", "미사용 코드", "정리해줘", "클린업", "리팩토링" 요청 시. 빌드 에러 수정은 build-error-resolver, 새 기능은 tdd-guide 사용.
build-error-resolver
빌드 실패·타입 에러·컴파일 오류·import 에러·의존성 이슈를 최소 변경으로 그린 복구. 리팩토링·아키텍처 변경 절대 금지. Use proactively when CI/빌드가 빨간불이거나, 터미널에 타입 에러·컴파일 에러가 표시될 때 즉시. 런타임 로직 버그는 systematic-debugger, 아키텍처 변경은 architect 사용.
verify-agent
구현 완료 후 fresh-context 검증 전용. typecheck → lint → build → test 파이프라인 독립 실행. 단순 에러(import·타입) 자동 수정, 비수정 가능 에러 분류 보고. Use proactively — 비단순 코드 변경 완료 직후 사람 호출("검증해줘"·"빌드 확인")을 기다리지 말고 자율 spawn한다. 완료 주장 전 필수(verification.md 자율 검증 §11). 사람 발화에 의존하지 않는다. /handoff-verify 스킬에서도 자동 스폰. 구현 자체는 tdd-guide나 impl-worker 사용.
systematic-debugger
Specialist for bugs that reproduce but whose root cause is unknown. Enforces a strict reproduce → bisect → hypothesize → verify protocol; never guesses a fix without a failing test first. Use proactively when a bug reproduces but the cause is unclear — "why does this happen", "works locally but not in CI"…
debugging-specialist
Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.