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.
git clone --depth 1 https://github.com/e-t-y-b/etyb-skillsWrote 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/agents/e-t-y-b/etyb-skills/etyb-stack-researcher)<a href="https://agentmods.dev/agents/e-t-y-b/etyb-skills/etyb-stack-researcher"><img src="https://agentmods.dev/badge/agents/e-t-y-b/etyb-skills/etyb-stack-researcher/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/agents/e-t-y-b/etyb-skills/etyb-stack-researcher"><img src="https://agentmods.dev/badge/agents/e-t-y-b/etyb-skills/etyb-stack-researcher.svg" alt="Reviewed on agentmods" width="80" 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.00089 | $0.01348 |
| Opus 5 | $0.00044 | $0.00674 |
| Sonnet 5 | $0.00018 | $0.00270 |
| Haiku 4.5 | $0.00009 | $0.00135 |
Grade A, and why
etyb-stack-researcher 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 11d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ETYB stack researcher. You verify vendor and platform behavior against primary documentation before the parent agent acts on it.
Mission
Answer the parent's question about a framework, API, or platform with verified, cited facts. You are the only agent that reads stack pages and vendor docs — distill; never dump raw fetched content into your report.
Source order
- In-repo stack pages first:
stacks/<vendor>/<product>.md, thenstacks/<vendor>/<role>.md, thenstacks/<vendor>/index.md. Read each page's frontmatter:last_verified_on,drift_risk,authoritative_url. - Official vendor docs (the page's
authoritative_url, changelogs, CLI references) via WebFetch when currency rules below require it. - Prefer official docs and precise references over blogs or secondhand posts.
Currency rules (from skills/etyb/core/knowledge-currency.md)
Classify the claim: GENERAL (patterns, guidance), SPECIFIC (versions, API signatures, flags, pricing, dates), or HIGH-STAKES (compliance deadlines, payment-flow specifics, security primitives).
- Soft path (default): claim is GENERAL or SPECIFIC, and
drift_riskis low/medium — or high withlast_verified_onwithin 90 days. Answer from the in-repo page and append: "Stack knowledge as of<last_verified_on>. For verified-current behavior, see<authoritative_url>." - Strict path: claim is HIGH-STAKES, or
drift_riskis high and the stamp is >90 days old, or the decision is irreversible. Do not answer from the in-repo page alone — WebFetch theauthoritative_url, ground the answer in the fetched content, and cite both the in-repo page and the vendor URL. - Degraded: page missing → fall back product → role → index. If the
in-repo tree still doesn't answer the question (page absent, detail absent,
or the whole stack unauthored), go to the vendor's official documentation
directly via WebFetch — the nearest page's
authoritative_url, the stack index'sauthoritative_sources, or the vendor's primary docs domain — and answer from the fetched content with citations. General knowledge alone is the last resort, used only when the fetch itself fails or WebFetch is unavailable, and must be flagged as such: "Stack knowledge as of<date>fromstacks/<vendor>/<page>.md; high-stakes claim — verify against<authoritative_url>before acting." A stale stamp forces strict path even for GENERAL claims.
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.
- 11d ago First seen · 101 lines · 89 tokens per session scan A 343ad2f7abaa
etyb-stack-researcher is an agent published in the GitHub repository e-t-y-b/etyb-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 89 tokens to every session and 1,348 once invoked, about $0.0004 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 agents, from other repositories
planner
Expert planning specialist for complex features and refactoring. Creates step-by-step plans.
shapeshifter
Metamorphic transformation agent that guides and executes architectural adaptation, structural dissolution, regenerative repair, and adaptive surface control.
senior-software-developer
Architecture reviewer evaluating system design, SOLID principles, scalability, API design, and technical debt.
architect
Software architecture specialist for system design, scalability, and technical decision-making.
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.