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 spytensor/openmozi --skill research-workflowgit clone --depth 1 https://github.com/spytensor/openmoziWrote 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/spytensor/openmozi/research-workflow)<a href="https://agentmods.dev/skills/spytensor/openmozi/research-workflow"><img src="https://agentmods.dev/badge/skills/spytensor/openmozi/research-workflow/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/spytensor/openmozi/research-workflow"><img src="https://agentmods.dev/badge/skills/spytensor/openmozi/research-workflow.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.00059 | $0.00516 |
| Opus 5.5 | $0.00024 | $0.00206 |
| Sonnet 5.5 | $0.00012 | $0.00103 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
research-workflow 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 1mo 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.
What it actually says
Research Workflow
How to Execute
- Decompose: Break the question into 2-5 sub-questions that can be researched independently.
- Search: Use web_search for each sub-question. Parallelize independent searches.
- Cross-verify: Check claims from multiple sources. Flag conflicting information.
- Synthesize: Combine findings into a structured answer with citations.
- Qualify: State confidence level and note gaps in available information.
Rules
- Never rely on training data alone for factual claims — always verify with web_search.
- Prefer primary sources (official docs, papers, announcements) over secondary ones.
- When sources conflict, present both sides and explain the discrepancy.
- Include dates for time-sensitive information.
- Clearly separate facts from your analysis or interpretation.
Freshness Self-Check (mandatory when the request says "latest", "recent", "最新", "近期", or implies now)
- Anchor: read the current date from the runtime time facts — that is "now", not your training data.
- Query with recency: include the current year (and month if relevant) in search queries; prefer provider recency filters when available.
- Date every source: extract each result's publication date. A result without a discoverable date is weak evidence for a "latest" claim.
- Compare before claiming: if the newest source you found is older than the request implies (e.g. a year-old report for a "latest report" request), say so explicitly — "the newest I could verify is X from " — instead of presenting it as current.
- If search is unavailable or returns nothing recent, state plainly what you could not verify. Never fill the gap from training data without labeling it as such.
Pitfalls
- Presenting training data as verified fact
- Citing a single source without cross-checking
- Omitting publication dates on time-sensitive topics
- Mixing opinion with established fact
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.
- 1mo ago First seen · 42 lines · 59 tokens per session scan A e789ac310b5e
research-workflow is a skill published in the GitHub repository spytensor/openmozi (484 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 516 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
workspaces
How an Open SWE workspace's sandbox image works and how to change it — create one, edit or fork an existing one, start from scratch, what setupscript and updatescript are for, why a nightly refresh failed, where the build logs are, and how to read a rebuild in progress. Read this whenever someone asks about…
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
audit-harness
Use when auditing HARNESS.md, pre-commit hooks, pre-push hooks, architecture gates, or CI workflows for tunacode-cli. This skill treats any mismatch, skipped gate, or failing check as a critical failure and requires manual one-by-one execution rather than make targets, batch wrappers, or summary-only audits.