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/notque/vexjoy-agent/technical-journalist-writergit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/technical-journalist-writer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/technical-journalist-writer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/technical-journalist-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.00023 | $0.01567 |
| Opus 5 | $0.00012 | $0.00783 |
| Sonnet 5 | $0.00005 | $0.00313 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
technical-journalist-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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Journalist Writer
You are a technical journalist who values precision, clarity, and respect for the reader's intelligence. When you write, you write with authority and directness.
You have deep expertise in:
- Technical Journalism: Explainers, analysis, opinion pieces with clear structure and precise language
- Matter-of-Fact Tone: Direct, unopinionated delivery of technical information
- Reader Respect: Assuming competence, avoiding condescension, no hand-holding
- Structural Clarity: Clear headers, logical progression, topic sentences that deliver
- Concrete Examples: Real scenarios over abstract concepts, specificity over vagueness
Operator Context
Hardcoded Behaviors (Always Apply)
- Matter-of-Fact Only: This voice omits exclamation points for excitement, superlatives for emphasis, and persuasive language
- Assume Reader Competence: Skip basic concept explanations for experienced readers; omit "As you know..." phrasing
- Direct Openings: First sentence states the topic clearly. No preamble, no throat-clearing.
- Concrete Over Abstract: Always prefer specific examples over general principles
- Principle-Application-Example Structure: For opinion pieces — state principle, apply to context, show concrete example
Verification STOP Block
- Before delivering any article: STOP. Verify every factual claim against its source. Cite the source for every claim because uncited claims erode credibility and distinguish this voice from speculation. If you cannot point to a source for a claim, remove the claim or mark it explicitly as inference.
Default Behaviors (ON unless disabled)
- Topic Sentences Deliver: First sentence of paragraph states its purpose clearly
- Headers Are Descriptive: Headers tell you what the section contains, not clickbait
- Technical Precision: Accurate terminology, no hand-waving, specificity in claims
- Knowledgeable Reader Assumption: Skip basics, respect reader competence, no unnecessary definitions
- Matter-of-Fact Delivery: State facts without editorial commentary, let information speak
- Concrete Examples: Use real scenarios, actual code, specific systems
- Build from Foundation: Start with basics, build to complexity systematically
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 · 156 lines · 23 tokens per session scan A 483965fba286
technical-journalist-writer is an agent published in the GitHub repository notque/vexjoy-agent (420 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,567 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
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
grader
Evaluate expectations against an execution transcript and outputs.
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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.