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 skills add trae-op/electron-modular-boilerplate --skill large-data-iterationgit clone --depth 1 https://github.com/trae-op/electron-modular-boilerplateWrote 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/skills/trae-op/electron-modular-boilerplate/large-data-iteration)<a href="https://agentmods.dev/skills/trae-op/electron-modular-boilerplate/large-data-iteration"><img src="https://agentmods.dev/badge/skills/trae-op/electron-modular-boilerplate/large-data-iteration.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.00053 | $0.00238 |
| Opus 5 | $0.00026 | $0.00119 |
| Sonnet 5 | $0.00011 | $0.00048 |
| Haiku 4.5 | $0.00005 | $0.00024 |
Grade A, and why
large-data-iteration 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 7d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 28 lines · 53 tokens per session scan A 769da5fd017f
large-data-iteration is a skill published in the GitHub repository trae-op/electron-modular-boilerplate (5 stars, last pushed 6mo ago), with no licence file. It adds 53 tokens to every session and 238 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-31.
Other skills, from other repositories
feishu-troubleshoot
A Feishu troubleshooting tool with FAQs and diagnostic commands. Feishu is a collaboration platform with online documents and workplace services.
business-ops-runbook-generator
Build an operational runbook with rollback paths for a recurring task or incident: capture the brief, infer failure modes, draft the runbook steps and checks, then define a rollback path for each failure mode. Use when the user wants a step-by-step runbook that an operator can follow under pressure, including what to…
termcanvas-agent-sync-debugging
Diagnose TermCanvas agentmux nodes that fail to appear and terminal canvases that become janky, resize repeatedly, or show corrupted/unreadable xterm text as terminal count grows, plus duplicate terminal views created after a release relaunch. Use when a child agent is missing, restored terminals duplicate or move to…
Debug (reproduce -> isolate -> fix)
Systematically diagnose and fix a bug instead of guessing.
error-collection
A structured record of confirmed engineering mistakes, their root causes, and checks that prevent them from returning. It uses evidence from real application behavior, not just successful builds.
flaky-test-triage
Use when a test passes and fails intermittently, behaves differently by order, machine, runtime, timing, or retry, or when the user asks to reduce test flakiness. Gather repeatable evidence, isolate nondeterminism, and repair the causal dependency without weakening test intent.