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/readmegit clone --depth 1 https://github.com/MacroMan5/AutomationHelper_pluginsWhat 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.00017 | $0.00761 |
| Opus 5 | $0.00009 | $0.00380 |
| Sonnet 5 | $0.00003 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
agents-documentation 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power Automate Agents
Ce dossier contient les agents spécialisés pour Power Automate.
flow-builder
Agent de construction de flows Power Automate
Fonctionnalité principale
Cet agent génère des flows Power Automate complets au format JSON prêt à copier-coller directement dans Power Automate via la fonction "Paste code".
Format de sortie garanti
Structure JSON exacte:
{
"definition": {
"$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"$connections": {
"defaultValue": {},
"type": "Object"
}
},
"triggers": { /* déclencheur du flow */ },
"actions": { /* toutes les actions */ },
"outputs": {}
},
"schemaVersion": "1.0.0.0"
}
Caractéristiques garanties
- ✅ JSON valide - Syntaxe correcte, pas d'erreurs
- ✅ Structure complète - Aucun placeholder
{...}, tout est défini - ✅ GUIDs valides - Tous les
operationMetadataIdsont des UUID correctement formatés - ✅ Expressions dynamiques - Syntaxe Power Automate correcte (
@triggerOutputs(),@body('action'), etc.) - ✅ Noms de connexion standards -
shared_sharepointonline,shared_onedrive, etc. - ✅ Dependencies runAfter - Chaînage correct des actions
- ✅ Copy-paste ready - Prêt à coller directement dans Power Automate
Validation automatique
Avant de renvoyer le JSON, l'agent vérifie:
- Syntaxe JSON (brackets, quotes, commas)
- Structure complète (root, definition, schemaVersion)
- Tous les champs obligatoires présents
- GUIDs au bon format
- Expressions Power Automate correctes
- Pas de texte placeholder
Utilisation
Fournir à l'agent:
- Description détaillée du flow souhaité
- Inputs (sources de données, déclencheurs)
- Outputs (destinations, résultats attendus)
- Logique métier (conditions, boucles, transformations)
L'agent génère:
- Analyse des requirements
- Architecture du flow
- JSON complet prêt à copier-coller
- Notes d'implémentation
- Instructions d'import
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 · 103 lines · 17 tokens per session scan A 96910db76bf8
agents-documentation is an agent published in the GitHub repository MacroMan5/AutomationHelper_plugins (3 stars, last pushed 10mo ago), licensed MIT. It adds 17 tokens to every session and 761 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-31.
Other agents, from other repositories
validation
How to run checks in this repository without rebuilding all 38 packages for a two-file change.
e2e-testing
pnpm expo run:ios pnpm expo run:android.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
playground-testing
Rozenite DevTools plugins. Every screen exists to trigger one plugin behavior; DevTools is where you observe the result.
plugin-development
src/tests/release-bundle.test.ts proving its DevTools panel cannot reach a shipped app; plugins exporting a bundler integration (./metro) guard that too. See release bundle testing.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.