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 skills/jonnyton/tinyassets/external-research-implicationsnpx skills add Jonnyton/TinyAssets --skill external-research-implicationsgit clone --depth 1 https://github.com/Jonnyton/TinyAssetsWrote 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/jonnyton/tinyassets/external-research-implications)<a href="https://agentmods.dev/skills/jonnyton/tinyassets/external-research-implications"><img src="https://agentmods.dev/badge/skills/jonnyton/tinyassets/external-research-implications.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.00061 | $0.03520 |
| Opus 5 | $0.00030 | $0.01760 |
| Sonnet 5 | $0.00012 | $0.00704 |
| Haiku 4.5 | $0.00006 | $0.00352 |
Grade A, and why
external-research-implications 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 — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
External Research Implications
Overview
Turn outside work into durable TinyAssets learning. Use this when the user points at a project, repo, research paper, article, architecture, product, benchmark, or competitor and asks for implications, integration, comparison, or a plan.
The output is not a generic summary. The job is to understand the outside work, map it against TinyAssets, decide what matters for our users, and leave behind a reusable plan or artifact that future sessions can act on.
Boundary with implementation precedent
Use this skill when a named outside source or a research finding may change TinyAssets strategy, PLAN/OpenSpec design truth, capability direction, or cross-task architecture. Use a repo search for precedent instead for a bounded search for external code examples that informs one implementation decision inside an already-authorized lane.
A scout source map is task-scoped implementation evidence covered by normal code review; it does not require its own opposite-provider research review. If the scout would broaden scope or change accepted design, stop implementation and promote the finding into this workflow and its cross-provider gate. This skill may invoke the scout for adjacent implementations, but remains responsible for durable implications, authority changes, and review.
Trigger Examples
- "Study this repo and tell us what it means for TinyAssets."
- "Read this paper and build an implementation plan."
- "Compare our architecture to this project."
- "What should we learn from this?"
- "Turn this research into steps toward integration."
- "Anytime I point an agent at a project/research paper/repo."
- "Find the most important frontier project for our direction."
- "Scan for paradigm shifts and tell us what to align with early."
Core Stance
TinyAssets users are people with MCP-connected chatbots. They should be able to steer, redesign, fork, evolve, and improve branches through conversation. The project should become more community-evolvable and self-improving, not more dependent on maintainers or local research harnesses.
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 · 382 lines · 61 tokens per session scan A 53a58543a36c
external-research-implications is a skill published in the GitHub repository Jonnyton/TinyAssets (1 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 3,520 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…