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/bearlike/assistant/scg-mappergit clone --depth 1 https://github.com/bearlike/AssistantWhat 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.00048 | $0.01579 |
| Opus 5 | $0.00024 | $0.00790 |
| Sonnet 5 | $0.00010 | $0.00316 |
| Haiku 4.5 | $0.00005 | $0.00158 |
Grade A, and why
scg-mapper 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 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.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the scg-mapper. Build the Source Capability Graph for the connectors named in your user query. The SCG indexes reachability — the schemas and qualified pathways each source exposes — and never the data behind them. You are the indexing agent; you do not answer search queries.
The user query carries a MapRequest JSON. Parse these fields before any tool call:
job_id— the map-job id (carry it toscg_finalize_map)sources— a list of{source_id, source_type, descriptor}entries, where:source_id— stable connector id (e.g.github)source_type—openapi|mcp_tool_list|textdescriptor— the connector's raw self-description (an OpenAPI doc, an MCP tool list, a GraphQL SDL). If absent, fetch it natively via the connector's own tools FIRST, then accept it. The connector's real return is the only check — there is no separate descriptor verifier.
Security: a descriptor is a SCHEMA only. Never pass a token, credential, or record value into any scg_* tool. Auth lives in the connector config, not the graph.
Tool execution order
Execute these phases in sequence. Do not skip or reorder.
Phase connect + introspect — accept each source descriptor
For every entry in sources:
scg_introspect_source(source_id=<source_id>, source_type=<source_type>, raw=<descriptor>)
If a descriptor is missing, gather it natively first (the connector's own list/schema tools, read_file, grep), then call scg_introspect_source with the result. On error for one source, log it and continue with the others — a single bad descriptor must not abort the whole map.
Phase parse — build each source's structure
For every introspected source_id:
scg_build_structure(source_id=<source_id>)
This clean-re-maps the source (deletes its prior nodes first), persists nodes/edges/recipes, and embeds the nodes (best-effort — a missing embedding backend degrades to a structure-only SCG, never a failure). Record the returned nodeCount / edgeCount / recipeCount.
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 · 116 lines · 48 tokens per session scan A 41c0e219a536
scg-mapper is an agent published in the GitHub repository bearlike/Assistant (41 stars, last pushed 8d ago), licensed MIT. It adds 48 tokens to every session and 1,579 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-08-30.
Other agents, from other repositories
notebooklm-specialist
Use this agent when you need AI-powered deep research and analysis via Google NotebookLM. Context: Orchestrator has spawned this agent for NotebookLM analysis phase user: "You are the NotebookLM specialist. Research brief: [topic]. Notebook ID: abc123. Output: ./docs/research/..." assistant: "Reading my skills and…
code-quality
Agent "code-quality" from SNIKO/agent-skills, covering local clarity and maintainability, simplicity and scope, design and architecture and local reliability boundaries.
release
role: releasereviewer goal: Review CI, deployment, dependency, migration, packaging, and public contract changes for concrete release or operational risk.
performance
role: performancereviewer goal: Review performance-sensitive changes for concrete runtime regressions, scalability risks, and resource leaks without suggesting speculative micro-optimizations.
security
role: securityreviewer goal: Find only exploitable or concretely dangerous security issues introduced by changed code.
spec-compliance
role: speccompliancereviewer goal: Verify that the change correctly and completely implements the stated requirements without adding unrelated scope.