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 Biraj2004/huashu-skills-english --skill huashu-research-engit clone --depth 1 https://github.com/Biraj2004/huashu-skills-englishWrote 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/biraj2004/huashu-skills-english/huashu-research-en)<a href="https://agentmods.dev/skills/biraj2004/huashu-skills-english/huashu-research-en"><img src="https://agentmods.dev/badge/skills/biraj2004/huashu-skills-english/huashu-research-en/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/biraj2004/huashu-skills-english/huashu-research-en"><img src="https://agentmods.dev/badge/skills/biraj2004/huashu-skills-english/huashu-research-en.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.00056 | $0.01988 |
| Opus 5.5 | $0.00022 | $0.00795 |
| Sonnet 5.5 | $0.00011 | $0.00398 |
| Haiku 4.5 | $0.00006 | $0.00199 |
Grade A, and why
huashu-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 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.
How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Skill
A structured web research workflow with one core objective: real-time persistence of research findings to prevent loss due to session interruptions.
When to Use
- Conducting preliminary research before writing an article
- Learning about new products, new technology, or recent releases
- Gathering competitor information or industry trends
- Any information-gathering task requiring multiple web searches
Execution Workflow
Step 1: Create the Research File Immediately
- Create the file before starting any searches
- Path:
_knowledge_base/research-<topic>-<YYYYMMDD>.md - Initial content includes: research objective, key questions, expected output
# [Topic] Research Notes
Research Date: YYYY-MM-DD
Research Objective: [One-sentence summary]
## Key Questions
1. [Question 1]
2. [Question 2]
3. [Question 3]
## Findings
(To be filled in progressively during research)
## Source List
(Append after each search)
Step 2: Search and Save Incrementally
- After every web search, immediately append findings to the file
- Tag each finding with the source URL and date
- Follow the source priority rules (see SHARED-RULES.md)
Step 3: Stage Summaries
- After every 3 searches, save a "stage summary" to the file
- Format:
### Stage Summary (Round N)+ current key findings
Step 4: Final Brief
At the end of research, organise the file into a structured brief:
## Research Conclusions
### Key Facts
1. [Fact 1] (Source: URL)
2. [Fact 2] (Source: URL)
### Source List
| Source | URL | Publication Date | Credibility |
param($m)
$inner = $m.Groups[1].Value
# Split by | and fix each cell separator
$cells = $inner -split '\|'
$fixedCells = $cells | ForEach-Object {
$cell = ---
name: huashu-research
description: Structured web research workflow that ensures research findings are saved incrementally to files and not lost due to session interruptions. Use when the user says "research", "search for information", "look this up", "find out about", or "latest information".
---
# Research Skill
A structured web research workflow with one core objective: real-time persistence of research findings to prevent loss due to session interruptions.
## When to Use
- Conducting preliminary research before writing an article
- Learning about new products, new technology, or recent releases
- Gathering competitor information or industry trends
- Any information-gathering task requiring multiple web searches
## Execution Workflow
### Step 1: Create the Research File Immediately
- Create the file **before** starting any searches
- Path: `_knowledge_base/research-<topic>-<YYYYMMDD>.md`
- Initial content includes: research objective, key questions, expected output
```markdown
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 · 259 lines · 56 tokens per session scan A e7f2678fa2a3
huashu-research is a skill published in the GitHub repository Biraj2004/huashu-skills-english (3 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 1,988 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-31.
Other skills, from other repositories
customer-journey-map
Construye un mapa de recorrido del cliente para un producto, servicio o experiencia. Úsalo cuando se te pida mapear un recorrido del cliente, crear un viaje del usuario, documentar puntos de contacto y puntos de fricción, o diseñar un mapa de experiencia. Produce un mapa de recorrido completo con etapas, puntos de…
user-research-synthesis
Analiza y sintetiza hallazgos de investigación de usuarios en insights estructurados y accionables. Úsalo cuando te proporcionen datos de investigación de usuarios, transcripciones de entrevistas, resultados de encuestas o feedback de usuarios que necesiten ser analizados y resumidos. Produce una síntesis temática con…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
explorer-interface-brief
Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an…
architectural-programme-brief
Turn a client's wishes into an architectural brief that can actually be designed against — the accommodation schedule, the adjacencies, the budget reality, and the constraints named before they become change orders. Use when asked to write an architectural brief, prepare a project brief for a building, run a client…
architecture-client-presentation
Present a design to a client so they can make a decision rather than react to a picture — the brief restated, the moves explained against it, the options with their trade-offs, and a specific decision requested. Use when asked to present a design to a client, prepare a design review meeting, present concept options…