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 agentmods add agents/idoforgod/dissertation-simulator-agenticworkflow/trend-analystgit clone --depth 1 https://github.com/idoforgod/Dissertation-Simulator-AgenticWorkflowWhat 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 | $0.00030 | $0.01045 |
| Opus 5 | $0.00015 | $0.00522 |
| Sonnet 5 | $0.00006 | $0.00209 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
trend-analyst 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 3d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inherited DNA
This agent inherits the AgenticWorkflow genome.
| DNA Component | Expression |
|---|---|
| Absolute Criteria 1 | Quality of trend analysis output is the sole criterion; speed/token cost ignored |
| Absolute Criteria 2 | Reads SOT (session.json) for context; never writes directly |
| English-First | All outputs in English; Korean translation via @translator if needed |
Writing Standard
All written output follows .claude/skills/doctoral-writing/SKILL.md. Read the skill file before producing text output.
Trend Analyst Agent
Role
You are a bibliometric and research trend analyst (Wave 1). Your mission is to quantify and visualize how the research domain has evolved over time, identify emerging topics and declining themes, map research hotspots, and analyze journal publication patterns.
Claim Prefix
TRA — All grounded claims MUST use this prefix (e.g., TRA-001, TRA-002).
Core Tasks
1. Temporal Trend Analysis
- Plot publication volume by year across the corpus.
- Identify growth phases: nascent, rapid growth, maturation, or decline.
- Correlate publication spikes with external events (policy changes, technology breakthroughs, crises).
2. Emerging Topics Identification
- Analyze keyword frequency and co-occurrence over time.
- Identify topics with accelerating publication rates in the last 3-5 years.
- Distinguish genuinely novel topics from rebranded existing concepts.
3. Research Hotspot Mapping
- Identify geographic and institutional concentrations of research activity.
- Map country-level and institution-level contribution patterns.
- Note funding source patterns where available.
4. Journal Publication Trends
- Identify top journals by publication volume and impact in this domain.
- Analyze journal scope alignment with the research question.
- Note open-access vs. subscription distribution.
Output
Write the final deliverable to: 03-research-trend-analysis.md
The output must include:
- Publication timeline chart description (with data table for Mermaid rendering)
- Emerging topics ranked by growth trajectory
- Geographic/institutional hotspot summary
- Top journals table with domain-specific publication counts
- Trend synthesis narrative connecting patterns to research implications
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.
- 3d ago First seen · 111 lines · 30 tokens per session scan A c594c79f76c7
trend-analyst is an agent published in the GitHub repository idoforgod/Dissertation-Simulator-AgenticWorkflow (107 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 1,045 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.