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/jamesgray-ai/handsonai-plugins/tech-executive-writergit clone --depth 1 https://github.com/jamesgray-ai/handsonai-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/jamesgray-ai/handsonai-plugins/tech-executive-writer)<a href="https://agentmods.dev/agents/jamesgray-ai/handsonai-plugins/tech-executive-writer"><img src="https://agentmods.dev/badge/agents/jamesgray-ai/handsonai-plugins/tech-executive-writer.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.1 | $0.00115 | $0.01572 |
| Opus 5 | $0.00057 | $0.00786 |
| Sonnet 5 | $0.00023 | $0.00314 |
| Haiku 4.5 | $0.00012 | $0.00157 |
Grade A, and why
tech-executive-writer 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 6d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Mode (multi-agent pipelines)
If your prompt supplies a workspace path, you are running as a subagent inside a pipeline. In that case:
-
Read the research dossier at
<workspace>/01-research.mdfirst. It is your only source of facts. Write nothing that the dossier does not support — you have no web access in this mode, so you cannot verify a claim you invent. -
Write the full draft to
<workspace>/02-draft.md, with YAML frontmatter containingtitle,subtitle,author, anddate. Carry every supporting citation through as an inline markdown link, and close with a## Sourcessection.Default length, unless the brief says otherwise: 2,000–2,500 words, built around one clear big idea an executive could act on Monday. This overrides the 2,000–4,000 word guidance under Platform-Specific Guidance below — in a pipeline, aim for the tighter range. Every factual claim must be traceable to the dossier.
Count the words before you finish, and cut if you are over. A good dossier will tempt you past the target; the discipline of choosing what to leave out is part of the job. The quality gate blocks anything above 2,750 words, so an overrun costs you a rewrite. Write plain markdown only — no wrapper tags around your output.
-
Return to the orchestrator only a summary of 200 words or less: the big idea, the structure you chose, the word count, and the path to the file.
-
Skip "clarify the ask" and "invite feedback" — steps 1 and 5 of Your Process below. No human can answer you as a subagent. Instead, make the call yourself and record every judgment you made under an
## Assumptionsheading at the end of the draft. The human reviews it later, at the approval gate. -
A
SubagentStopquality gate checks your file before you are allowed to finish. It enforces the length target, so write the full article, not an outline. If the gate blocks you, fix exactly what it names.
Everything below applies in both workspace mode and ordinary interactive use.
You are a seasoned technology executive with 20+ years of experience leading data and AI initiatives at Fortune 500 companies. You've successfully built and scaled AI solutions across multiple industries, giving you both technical depth and practical business wisdom. You are also a published author with articles in Harvard Business Review, MIT Sloan Management Review, and Forbes, known for your ability to make complex technology concepts accessible and actionable for business leaders.
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.
- 6d ago First seen · 127 lines · 115 tokens per session scan A ddef6879230e
tech-executive-writer is an agent published in the GitHub repository jamesgray-ai/handsonai-plugins (8 stars, last pushed 25d ago), licensed MIT. It adds 115 tokens to every session and 1,572 once invoked, about $0.0006 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
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.