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 commands/jannleo/telinksdk-builder-mcp/loggit clone --depth 1 https://github.com/JannLeo/telinksdk-builder-mcpWrote 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/commands/jannleo/telinksdk-builder-mcp/log)<a href="https://agentmods.dev/commands/jannleo/telinksdk-builder-mcp/log"><img src="https://agentmods.dev/badge/commands/jannleo/telinksdk-builder-mcp/log.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 | $0.00000 | $0.00284 |
| Opus 5 | $0.00000 | $0.00142 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
log 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 4d 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
/log analyze
Analyze a captured serial log file for key events like boot stages, pairing, errors, OTA progress, and version strings.
Usage
/log analyze # Auto-select newest .log file, all patterns
/log analyze --file _ota_car.log # Specific log file
/log analyze --patterns boot,error # Only boot and error patterns
/log analyze --context 5 # 5 lines of context around each match
/log analyze --max-events 50 # Limit to 50 events
Pattern Groups
| Pattern | Matches |
|---|---|
boot |
Bootloader start, FW_ADDRESS, boot_copy_data, jump to app |
pair |
Pairing start/success/timeout |
error |
ERROR, FAIL, HARD FAULT, WDT reset, assert, crash |
ota |
OTA start/progress/done/fail, pkt# received/sent |
version |
fw_ver, FW_VERSION, version strings |
wake |
wakeup, wake from sleep, suspend, resume |
reset |
reset, reboot, cpu_wakeup_init |
Default: all 7 patterns.
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.
- 4d ago First seen · 33 lines · 0 tokens per session scan A c1205df85b37
log is a command published in the GitHub repository JannLeo/telinksdk-builder-mcp (1 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 284 tokens. 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-31.
Other commands, from other repositories
observe
部屋を能動的に観察する。3つの基本ブロックを自由に選びながらループし、受動的なスナップショットではなく発見のある観察を行う。.
model
Check if an AI model fits on your GPU before downloading.
tapeout
Produce a complete, fab-ready export bundle for a routed board — or refuse loudly. Superset of /kct:manufacturing-readiness: runs the three sign-off pre-gates, then adds a BOM part-number-resolution gate, a per-rule warning-review gate (assembly-affecting warnings block unless explicitly acknowledged), schematic +…
compliance-matrix
Gestiona matriz de conformidad con estándares regulatorios (CE, FCC, UL, RoHS, ISO). Permite definir estándares, trackear estado de requisitos, vincular evidencia, identificar gaps y generar reportes de cumplimiento.
eol-report
EOL/EOS risk report — devices, OS versions, and firmware approaching or past end-of-life/end-of-support, prioritized by criticality.
cisco-catalyst-ta-setup
Configure and validate the Cisco Catalyst Add-on (TAciscocatalyst), including SD-WAN API/BFD, UTD and ZBFW syslog routing, Cyber Vision, ISE, Catalyst Center, and the beta IOS-XE CLI collector.