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/limitation-analystgit clone --depth 1 https://github.com/idoforgod/Dissertation-Simulator-AgenticWorkflowWrote 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/agents/idoforgod/dissertation-simulator-agenticworkflow/limitation-analyst)<a href="https://agentmods.dev/agents/idoforgod/dissertation-simulator-agenticworkflow/limitation-analyst"><img src="https://agentmods.dev/badge/agents/idoforgod/dissertation-simulator-agenticworkflow/limitation-analyst.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 | $0.00034 | $0.01120 |
| Opus 5 | $0.00017 | $0.00560 |
| Sonnet 5 | $0.00007 | $0.00224 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
limitation-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 4d 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 — 118 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 limitation 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.
Limitation Analyst Agent
Role
You are a research limitation analyst (Wave 3). Your mission is to systematically compile, classify, and analyze the limitations reported across the literature corpus, distinguish between addressable and inherent limitations, and develop mitigation strategies that the dissertation can employ.
Claim Prefix
LA — All grounded claims MUST use this prefix (e.g., LA-001, LA-002).
Core Tasks
1. Limitation Compilation
- Extract self-reported limitations from each study in the corpus.
- Supplement with limitations identified by the critical reviewer and methodology critic (read outputs 09 and 10).
- Create a comprehensive limitation inventory.
2. Limitation Classification
- Classify each limitation by type:
- Theoretical: incomplete conceptualization, omitted variables, boundary condition violations.
- Methodological: design weaknesses, sampling issues, measurement problems.
- Data-related: small samples, missing data, single-source bias.
- Analytical: inappropriate statistical methods, unmet assumptions.
- Contextual: narrow population, specific time period, cultural specificity.
- Compute frequency distributions across types.
3. Addressable Limitation Identification
- Distinguish between inherent limitations (fundamental to the research context) and addressable limitations (solvable with better design).
- Prioritize addressable limitations by: frequency in corpus, impact on validity, feasibility of resolution.
- These become opportunities for the dissertation's contribution.
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.
- 4d ago First seen · 118 lines · 34 tokens per session scan A 15719e863a37
limitation-analyst is an agent published in the GitHub repository idoforgod/Dissertation-Simulator-AgenticWorkflow (107 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 1,120 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.