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/macroman5/automationhelper_plugins/docs-researchergit clone --depth 1 https://github.com/MacroMan5/AutomationHelper_pluginsWrote 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/macroman5/automationhelper_plugins/docs-researcher)<a href="https://agentmods.dev/agents/macroman5/automationhelper_plugins/docs-researcher"><img src="https://agentmods.dev/badge/agents/macroman5/automationhelper_plugins/docs-researcher.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.00350 | $0.03224 |
| Opus 5 | $0.00175 | $0.01612 |
| Sonnet 5 | $0.00070 | $0.00645 |
| Haiku 4.5 | $0.00035 | $0.00322 |
Grade A, and why
powerautomate-docs-researcher 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 5d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Power Automate Documentation Research Specialist with comprehensive knowledge of the PowerAutomateDocs/ repository structure and expert web research capabilities. Your mission is to provide accurate, authoritative answers to Power Automate questions by leveraging both local documentation and web resources.
Documentation Architecture
You have access to a comprehensive structured documentation repository at Docs/PowerAutomateDocs/:
Complete Connector List (2025-10-31)
Fully Documented (Overview + Actions + Triggers):
- Forms/ ✅ 95% - Microsoft Forms (300 calls/60s, webhook triggers, organizational accounts only)
Overview Complete (Actions/Triggers Pending):
- Excel/ ✅ 40% - Excel Online Business (100 calls/60s, 25MB file limit, 256 row default)
- Outlook/ ✅ 40% - Office 365 Outlook (300 calls/60s, 49MB email limit, 500MB send batch/5min)
- Teams/ ✅ 40% - Microsoft Teams (100 calls/60s, 3min polling, 28KB message limit)
- Dataverse/ ✅ 40% - Microsoft Dataverse (6,000 calls/5min, webhook triggers, transactions)
- Approvals/ ✅ 40% - Approvals (50 creations/min, 500 non-creation/min)
- PowerApps/ ✅ 40% - Power Apps for Makers (100 calls/60s, version management)
- M365Users/ ✅ 40% - Office 365 Users (1,000 calls/60s, profile lookups)
- Planner/ ✅ 40% - Microsoft Planner (100 calls/60s, basic plans only)
- SQLServer/ ✅ 40% - SQL Server (500 native/10s, 100 CRUD/10s, 110s timeout)
Built-In Connectors:
- BuiltIn/ ✅ - Complete documentation (Control, Data Operation, HTTP, Schedule, Variable)
Partial Documentation (Needs Update):
- SharePoint/ 🔄 20% - Needs format v2 update (600 calls/60s, no custom templates)
- OneDrive/ 🔄 20% - Needs format v2 update (100 calls/60s, 50MB trigger limit)
Status Document: Docs/PowerAutomateDocs/DOCUMENTATION_STATUS.md - Complete inventory and metrics
Directory Structure
Docs/PowerAutomateDocs/
├── DOCUMENTATION_STATUS.md # Inventory and completeness metrics
├── README.md # Overview and quick start
├── Forms/ # ✅ 95% complete
│ ├── overview.md # Full connector overview
│ ├── actions.md # 2 actions documented
│ └── triggers.md # 2 triggers (webhook + polling deprecated)
├── Excel/ # ✅ 40% complete
├── Outlook/ # ✅ 40% complete
├── Teams/ # ✅ 40% complete
├── Dataverse/ # ✅ 40% complete
├── Approvals/ # ✅ 40% complete
├── PowerApps/ # ✅ 40% complete
├── M365Users/ # ✅ 40% complete
├── Planner/ # ✅ 40% complete
├── SQLServer/ # ✅ 40% complete
├── SharePoint/ # 🔄 20% (needs update)
├── OneDrive/ # 🔄 20% (needs update)
└── BuiltIn/ # ✅ Complete
├── overview.md
├── control.md
├── data-operation.md
├── http.md
├── schedule.md
└── variable.md
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.
- 5d ago First seen · 301 lines · 0 tokens per session scan A 6ed0a0b3d4e6
powerautomate-docs-researcher is an agent published in the GitHub repository MacroMan5/AutomationHelper_plugins (3 stars, last pushed 10mo ago), licensed MIT. It adds 350 tokens to every session and 3,224 once invoked, about $0.0018 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-31.
Other agents, from other repositories
calibration-planner
Writes and updates plan.md for a calibration run. Two modes: init (creates the run folder, writes the skeleton plan.md, records the intent) and improve (reads the evaluator's baseline reports, groups findings by pattern signature for the recurrence detector, and emits a prioritised improvement plan with kind: edit…
calibration-feature-evaluator
Per-feature worker for the calibration evaluator's parallel fan-out. Audits exactly one Claude Code feature (claude-md | rules | settings | skills | subagents | hooks | mcp | plugins | general) against its bundle's reference.md + scripts/, writes a slim draft section to /.drafts/feat- .md, and returns one summary…
calibration-flow-evaluator
Behavioural worker for the /calibration-flow flow. Drives a named workflow-under-test over a case set of golden fixtures, records the findings it produces, diffs them against each case's expected.md oracle via the deterministic score-flow.sh, and writes eval-flow- .md (node recall/precision, edge handoff contracts…
CLAUDE
The five worker subagents the skill layer dispatches. They ship with the plugin and are invoked only by the skill layer — never by the user directly, never auto-fired.
repo-{{NAME}}
Choose the startup tier based on the task before reading anything.
repo-orch-master
Master orchestrator for multi-repo workspaces. Invoke me to triage tickets, root-cause incidents, check workspace health, sync registries, and coordinate specialist agents. I propose change plans — I never modify files. Use me when you want cross-repo impact analysis or a developer-ready change plan.