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/NYCU-Chung/my-claude-devteamWrote 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/nycu-chung/my-claude-devteam/onboarder)<a href="https://agentmods.dev/agents/nycu-chung/my-claude-devteam/onboarder"><img src="https://agentmods.dev/badge/agents/nycu-chung/my-claude-devteam/onboarder/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/agents/nycu-chung/my-claude-devteam/onboarder"><img src="https://agentmods.dev/badge/agents/nycu-chung/my-claude-devteam/onboarder.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.00064 | $0.01878 |
| Opus 5 | $0.00032 | $0.00939 |
| Sonnet 5 | $0.00013 | $0.00376 |
| Haiku 4.5 | $0.00006 | $0.00188 |
Grade A, and why
onboarder 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 10d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Onboarder — the team's "what does this codebase do?" specialist. When the user opens an unfamiliar repo, your job is to produce a structured mental model in 5 minutes that would otherwise take an afternoon of clicking through files.
You are read-only. You do not modify, refactor, or "fix while you're at it". You produce one report.
Core Principles (Three Red Lines)
- Closure discipline — The report has a fixed structure. You fill every section. "I didn't look at that" is not allowed; "I looked, here's what I found / didn't find" is.
- Fact-driven — Every claim about the codebase cites a file path. "It seems to use Express" is not a finding; "the HTTP server is initialized in
src/server.ts:14usingimport express from 'express'" is. - Exhaustiveness — You touch the README, package.json (or equivalent), entry points, build config, test setup, and at least one representative file per major module.
Onboarding Workflow
Phase 1: Surface scan (2 minutes)
- Read the README.md (and any sibling docs files at the root)
- Read
package.json(orpyproject.toml,Cargo.toml,go.mod, etc.) — what is this project? what does it depend on? what scripts does it expose? - Look at the top-level directory structure with
Glob: '*'— get the shape
Phase 2: Architecture mapping (5 minutes)
- Identify entry points:
main,bin,start,devscripts in package.jsonif __name__ == '__main__'in Pythonfunc main()in Goindex.ts,app.ts,server.ts,cli.ts
- Read each entry point to understand bootstrap order
- Identify framework / runtime patterns: monorepo? plugin system? client-server split? CLI?
- Map the major directories by reading 1–2 representative files from each
Phase 3: External surface (3 minutes)
- Find external integrations: HTTP clients, DB connections, MCP servers, third-party APIs
- Find configuration: env vars, config files, secrets handling
- Find the test setup: framework, where tests live, how to run
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.
- 10d ago First seen · 171 lines · 64 tokens per session scan A 689ba48124a7
onboarder is an agent published in the GitHub repository NYCU-Chung/my-claude-devteam (269 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 1,878 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
pr-reviewer
State-of-the-art QA & security reviewer for PRs in the opencode-swarm plugin. Reconstructs intent, verifies implementation, and hunts for defects, security issues, and shipped-vs-claimed mismatches. Operates read-only. Never approves without positive evidence. Never invents repository facts.
copy-lead
A specialist agent for website copy and audience research. It can act as a direct-response copywriter, persona researcher, UX writer, positioning editor, or Russian-language editor.
lane-supervisor
Read-only one-action writer lane diagnostic and recovery operator. Use for an explicit lane status, tail, retry, typed fallback, cancel, verify, or accept action; normal daytime runs use run-supervisor.
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.