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/nxtg-ai/forge-plugin/wordsmithgit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWhat 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.00000 | $0.01963 |
| Opus 5 | $0.00000 | $0.00981 |
| Sonnet 5 | $0.00000 | $0.00393 |
| Haiku 4.5 | $0.00000 | $0.00196 |
Grade A, and why
wordsmith 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wordsmith
The copywriter who makes developers install, click, and trust -- writing text that earns its place sentence by sentence, with a kill list for every hollow adjective and AI-detectable word.
| Level | L1 Vibe Coder |
| Category | Executive & Strategy |
| Model | Sonnet |
What It Does
The Wordsmith writes text that makes people do things: install, click, buy, read further, trust. Every sentence earns its place or gets cut. It writes like a senior engineer explaining something to a peer over coffee -- direct, opinionated, concrete, human, and honest.
It covers every user-facing text surface: landing page copy (headlines, value props, CTAs using PAS, AIDA, and 4U formulas), technical blog posts (teaching through storytelling, code blocks every 2-3 paragraphs), README files (install command above the fold, three-command quickstart), product descriptions, email sequences (onboarding drips, activation campaigns), social media posts (platform-native voice for Twitter, LinkedIn, Reddit), documentation, error messages (what happened, why, how to fix it), CLI help text (examples mandatory, zero prose), and changelog entries (user impact, not internal diffs).
The agent maintains a strict kill list of AI-detectable words (delve, tapestry, robust, holistic, seamless) and hollow adjectives (powerful, flexible, easy-to-use, blazing fast). Every instance is replaced with specific evidence. "Powerful" becomes "handles 10K concurrent connections." "Blazing fast" becomes "47ms p99 latency." "Easy to use" becomes a three-line code example. If an adjective survives without evidence, the Wordsmith failed.
When to Use It
- Landing page copy: When you need headlines that stop scrolling, value propositions that resonate, and CTAs that convert.
- README rewrite: When your README reads like a spec sheet and nobody is installing. The Wordsmith makes the install command the first thing visible and the value proposition undeniable.
- Error message redesign: When your error messages say "Something went wrong" and users do not know what to do next.
- Technical blog post: When you need a blog post that teaches through story, balances depth with readability, and includes working code examples.
- Changelog writing: When you need to turn a commit log into a changelog that tells users what changed for them, not what changed in the code.
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 · 142 lines · 0 tokens per session scan A 55dbd9eb3cbb
wordsmith is an agent published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,963 tokens. 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
code-reviewer
Reviews code for project guideline compliance, bugs, and quality issues. Use after writing code, before commits, or before PRs. Specify files to review or defaults to unstaged git changes. High-confidence issues only (80+) to minimize noise.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
data-pipeline-engineer
Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
emulate-engineer
Stateful API emulation via Vercel emulate. Seeds GitHub/Vercel/Google/Slack/Apple/Entra/AWS/MongoDB/Okta/Resend/Stripe/Clerk/Linear, webhooks, port isolation, Next.js adapter. Use to replace flaky API mocks.
TESTING
This document provides comprehensive guidance for testing the Multi-Agent Networks feature in NeuroLink.