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 runxhq/runx --skill ecosystem-briefgit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/ecosystem-brief)<a href="https://agentmods.dev/skills/runxhq/runx/ecosystem-brief"><img src="https://agentmods.dev/badge/skills/runxhq/runx/ecosystem-brief/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/skills/runxhq/runx/ecosystem-brief"><img src="https://agentmods.dev/badge/skills/runxhq/runx/ecosystem-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.00671 |
| Opus 5 | $0.00010 | $0.00336 |
| Sonnet 5 | $0.00004 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
ecosystem-brief 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 6d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ecosystem Brief
Produce one time-bounded update on what changed, why it matters, and what an operator should do with that information. This is the focused monitoring variant of the research and content chain: a sharp decision brief, not a generic news roundup or an article padded from weak signals.
Lead with the operational implication. Then show the verified change, sources, inference, uncertainty, and recommended posture. Connect a signal to product, trust, distribution, positioning, or catalog work only when the evidence supports that connection.
Composes
ghostwrite#draftresearch#research
When to use it
Use ecosystem-brief for daily or periodic monitoring of a bounded market,
technology, project set, or competitive surface. Use deep-research when the
question is durable and needs a fuller decision memo. Use content-pipeline
when the principal outcome is reader-facing publication rather than operator
awareness.
How the chain works
- Supply governed source packets and an explicit
as_oftime. - A deterministic freshness gate rejects missing provenance, future-dated observations, and sources older than the declared window.
researchverifies citations and separates evidence from inference.ghostwriteturns the ready packet into a concise brief whose claims remain bound to admitted source digests.
The brief remains local. A Slack, email, social, or publication skill must own any outward notification and its approval, idempotency, and provider readback.
Inputs and result
objectiveidentifies the monitoring question or decision.source_packetsprovide governed evidence.as_ofis the explicit evaluation time;max_age_hoursdefines freshness.audience,channel,domain,operator_context, andtarget_entitiesscope relevance without becoming evidence themselves.
The result includes the freshness report, citation-validated research packet,
and evidence-bound brief. It returns needs_more_evidence when no source
survives freshness and provenance checks, and not_worth_publishing when the
change is real but offers no useful posture.
What ships with it
2 files 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.
- 6d ago First seen · 77 lines · 19 tokens per session scan A 6f4fa6b0f4b4
ecosystem-brief is a skill published in the GitHub repository runxhq/runx (84 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 671 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
dd-sourcing
Document sources properly for due diligence reports. Use when citing any external data, ensuring full traceability and auditability of findings.
dd-verification
Verify claims in pitch decks and founder statements using multiple independent sources. Use when analyzing any claim about market size, traction, team background, or competitive positioning.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.