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-topic-gen-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-topic-gen-en)<a href="https://agentmods.dev/skills/biraj2004/huashu-skills-english/huashu-topic-gen-en"><img src="https://agentmods.dev/badge/skills/biraj2004/huashu-skills-english/huashu-topic-gen-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-topic-gen-en"><img src="https://agentmods.dev/badge/skills/biraj2004/huashu-skills-english/huashu-topic-gen-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.00053 | $0.00736 |
| Opus 5.5 | $0.00021 | $0.00294 |
| Sonnet 5.5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
huashu-topic-gen 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Topic Generation
Quickly generate 3–4 WeChat article topic directions, each including a title, outline, and pros/cons analysis.
When to Use
- After saving a brief
- When the user says "give me some topic ideas" or "suggest a few directions"
- Step 3 of the article creation workflow (topic discussion)
Core Features
- Provide 3–4 topic directions: Each from a different angle
- Each topic includes: Title, core angle, outline, workload estimate, pros/cons analysis
- Wait for user selection: Do not assume which one they will choose
Topic Direction Types
1. In-Depth Review
- Angle: Comprehensive testing + data comparison
- Suitable for: New products, new technologies
- Workload: ⭐⭐⭐ (requires real testing)
2. Practical Tutorial
- Angle: Step-by-step guide + replicable
- Suitable for: Tool usage, technical practice
- Workload: ⭐⭐ (requires step verification)
3. Insight & Opinion
- Angle: Unique perspective + deep thinking
- Suitable for: Industry trends, methodology
- Workload: ⭐ (primarily driven by thinking)
4. Case Study Breakdown
- Angle: Success case + method extraction
- Suitable for: Growth cases, product cases
- Workload: ⭐⭐ (requires case gathering)
Topic Template
## Topic 1: [Compelling Title]
**Core Angle**: xxx
**Workload Estimate**: ⭐⭐ (Medium)
**Does it require real testing**: Yes / No
### Outline
1. Opening: xxx
2. Core Section 1: xxx
3. Core Section 2: xxx
4. Closing: xxx
**Estimated Word Count**: 3,000 words
### Advantages
- ✅ Advantage 1
- ✅ Advantage 2
### Disadvantages
- ⚠️ Disadvantage 1
- ⚠️ Disadvantage 2
Title Strategies
Compelling title formulas:
- Comparison type: "A vs B — How Big Is the Gap?"
- Pain point type: "Why Does XX Always Fail?"
- Results type: "I Used XX and Achieved YY in 3 Months"
- Reveal type: "The Truth Behind XX"
- List type: "5 Methods That Will XXX"
Notes
- Each topic angle must be clearly different
- Pros/cons analysis should be honest (don't exaggerate)
- Workload estimates should be accurate
- Wait for the user to choose — never assume
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 · 102 lines · 53 tokens per session scan A a6e5ebee0337
huashu-topic-gen is a skill published in the GitHub repository Biraj2004/huashu-skills-english (3 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 736 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…