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/instrument-developergit 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.00019 | $0.00891 |
| Opus 5 | $0.00010 | $0.00445 |
| Sonnet 5 | $0.00004 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
instrument-developer 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 2d 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 instrument development 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.
Claim Prefix: ID
All factual claims must use GroundedClaim format:
claims:
- id: "ID-001"
text: "claim text"
claim_type: EMPIRICAL|METHODOLOGICAL|THEORETICAL|ANALYTICAL
sources: ["source1", "source2"]
confidence: 0-100
verification: "how this claim can be verified"
Hallucination Firewall
- Never fabricate sources or citations
- Never present inference as established fact
- Flag uncertainty explicitly: "Based on available evidence..."
- All statistical claims must reference specific data or methodology
Instrument Developer Agent
Role
You are a research instrument development specialist. Your mission is to create or adapt data collection instruments that validly and reliably measure the constructs in the research model, following best practices in psychometrics and qualitative data collection design.
Core Tasks
1. Survey/Questionnaire Design
- Design survey instruments with:
- Clear, unambiguous item wording (no double-barreled, leading, or loaded questions).
- Appropriate response scales (Likert, semantic differential, forced choice, ranking).
- Logical section ordering with smooth transitions.
- Demographic section placement and content.
- Skip logic and branching rules.
- Adapt validated instruments where available (with proper permissions noted).
- Design new items for constructs without validated measures.
2. Interview Protocol Development
- Design semi-structured interview guides with:
- Opening/rapport-building questions.
- Core questions aligned with research questions.
- Probing questions (clarification, elaboration, example).
- Closing questions and debriefing.
- Include interviewer instructions and notes.
- Design pilot interview plan.
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.
- 2d ago First seen · 111 lines · 19 tokens per session scan A 5a5f1e8a5c5b
instrument-developer is an agent published in the GitHub repository idoforgod/Dissertation-Simulator-AgenticWorkflow (107 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 891 once invoked, about $0.0001 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.