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 yuri-semenenko/ai-engineering-workspace --skill researchgit clone --depth 1 https://github.com/yuri-semenenko/ai-engineering-workspaceWrote 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/yuri-semenenko/ai-engineering-workspace/research)<a href="https://agentmods.dev/skills/yuri-semenenko/ai-engineering-workspace/research"><img src="https://agentmods.dev/badge/skills/yuri-semenenko/ai-engineering-workspace/research.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.00000 | $0.00774 |
| Opus 5 | $0.00000 | $0.00387 |
| Sonnet 5 | $0.00000 | $0.00155 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
research 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.
How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research
Turn a technical question into a decision you can defend: evidence from primary sources, a cited comparison, and a recommendation that states its own uncertainty. The output feeds an RFC or ADR; it is not the decision document itself. Depth is proportional to the blast radius of the decision, not to how much you could read.
The loop
- Frame the question and the criteria. Pin down the decision this feeds and the axes that will matter (performance, DX, bundle size, maintenance, license, lock-in, team familiarity — whichever apply). Those axes become the columns of the matrix. If the question is too broad to answer (no budget, scale, or constraint), ask one or two clarifiers and stop; a vague question yields a vague matrix.
- Go to primary sources. Prefer official docs, specs, changelogs, benchmarks, and the source itself over blog posts and SEO content. Read the repo's own constraints too (existing deps, runtime, team). Date volatile facts — ecosystem claims rot.
- Capture evidence, cite as you go. Each finding is a claim plus where it came from. Separate what the source says from your inference. Keep a short trail of sources kept and dropped, with the reason, so the evidence is auditable.
- Surface contradictions, do not smooth them. When sources conflict, say so explicitly and say which you trust and why. What you cannot resolve becomes an open question, not a silent pick.
- Build the decision matrix. Options as rows (always include "do nothing / defer"), the criteria from step 1 as columns. Fill cells with cited evidence, not impressions.
- Recommend with uncertainty. State the recommendation, your confidence, what would change it, and what remains unknown. Do not overstate a thin evidence base.
- Hand off. The matrix and recommendation are the input to /rfc (Options, Trade-offs) or /adr (Alternatives Considered). Stop there — research is not the decision doc.
Rules
- Primary sources over secondary. Cite every load-bearing claim; date the volatile ones.
- Not a literature review and not a full research-report harness: bound the search to what the decision needs.
- Flag uncertainty explicitly; keep contradictions visible rather than resolving them by omission.
- No marketing prose, no false confidence. A recommendation the evidence does not support is worse than "we don't know yet, here is how to find out".
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 · 31 lines · 0 tokens per session scan A e66e86429d64
research is a skill published in the GitHub repository yuri-semenenko/ai-engineering-workspace (1 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 774 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 skills, from other repositories
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
My Skill
Content here.
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
spec-authoring
Reference material for writing product, technical, and operational specifications (work-item priorities, requirement families, success criteria). Loaded on demand by specify-feature; not directly invokable.
audit
Audits recent work against its Definition of Done and project patterns. Runs the test suite, compares code against the spec, and reports PASS / PARTIAL / FAIL. Also runs the Critical Gate — a safety scan of the diff for destructive or dangerous operations. Generates an incremental prompt pack for any gaps found. With…