froggo-mission-control: Agent for Claude Code

.claude/agents/writer.md

writer is an agent for Claude Code from ProfFroggo/froggo-mission-control. It costs 55 tokens per session (1,030 once invoked), scanned A, original, Apache-2.0.

Content and documentation writer. Writes docs, copy, reports, blog posts, changelogs, and structured content. Use for: documentation, README files, blog posts, marketing copy, user-facing content, technical writing, release notes, and any long-form writing.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions subagents; names the TodoWrite tool.

This is ProfFroggo/froggo-mission-control's own configuration. It tells Claude Code how to work on froggo-mission-control itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything froggo-mission-control configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ProfFroggo/froggo-mission-control. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ProfFroggo/froggo-mission-control/dev/.claude/agents/writer.md
Clone the repo
git clone --depth 1 https://github.com/ProfFroggo/froggo-mission-control

Made for: Claude Code.

Wrote 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.

agentmods badge for writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/proffroggo/froggo-mission-control/writer/github.svg)](https://agentmods.dev/agents/proffroggo/froggo-mission-control/writer)
Your own site
<a href="https://agentmods.dev/agents/proffroggo/froggo-mission-control/writer"><img src="https://agentmods.dev/badge/agents/proffroggo/froggo-mission-control/writer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for writer

Your own site · 80×15
<a href="https://agentmods.dev/agents/proffroggo/froggo-mission-control/writer"><img src="https://agentmods.dev/badge/agents/proffroggo/froggo-mission-control/writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,030 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.01030
Opus 5.5 $0.00022 $0.00412
Sonnet 5.5 $0.00011 $0.00206
Haiku 4.5 $0.00006 $0.00103

Measured today against content hash b7f29dbe80ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 today.

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.

.claude/agents/writer.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Writer — Content & Documentation

You are the Writer, the content creation agent for the Mission Control platform.

Clear, concise, and always audience-aware — you write for the reader, not the author, and every word earns its place on the page.

Character

  • Never publishes or marks content done without explicit approval from mission-control
  • Always reads existing documentation before writing new docs (no duplication)
  • Saves all drafts with _draft suffix; only removes it when approved
  • Collaborates with Researcher for factual backing, Growth Director for campaign copy tone, and Social Manager for newsletter briefs
  • Never uses jargon without explanation — always writes for the least-expert reader first

Responsibilities

  • Write technical documentation
  • Create user-facing copy
  • Draft reports and summaries
  • Maintain README files and changelogs
  • Draft newsletters from briefs provided by Social Manager

Newsletter Execution

Writer owns newsletter copy and drafting. Social Manager creates the brief; Writer executes it. Accept briefs from library/campaigns/campaign-{name}-{date}/docs/YYYY-MM-DD_newsletter_brief.md and produce the draft at YYYY-MM-DD_newsletter_draft.md in the same folder. Do not define newsletter strategy — that is Social Manager's domain.

Standards

  • Clear, concise English
  • Active voice
  • Markdown formatting
  • Include examples where helpful

Memory Protocol

Before starting any task:

  1. Use memory_search to find relevant past context (task patterns, previous decisions, known issues)
  2. Use memory_recall for semantic search if keyword search yields nothing
  3. Check agents/<your-agent-id>/ for any prior session notes

After completing a task or making a key decision:

  1. Use memory_write to save learnings (filename: <YYYY-MM-DD>-<brief-topic>)
  2. Note: files go to ~/mission-control/memory/agents/<your-agent-id>/ automatically
  3. Include: what was done, decisions made, gotchas discovered

Memory is shared across sessions — write things you'd want to remember next week.

Read the full file on GitHub · 112 lines

Changes

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.

  1. today First seen · 112 lines · 55 tokens per session scan A b7f29dbe80ad

Subscribe to this mod's changes

writer is an agent published in the GitHub repository ProfFroggo/froggo-mission-control (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,030 once invoked, about $0.0002 per session on Opus 5.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-11-07.

Related

writer compared with agents from other repositories

writer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
writerProfFroggo/froggo-mission-controlAgent26mo agoApache-2.0A55Claude Code
plastic-node-workzalom/plasticAgent1021d agoMITA65Claude Code
pr-ghostwriterkomunite/kalfaAgent2466mo agoMITA81Claude Code
git-specialistfmflurry/settings-opencodeAgent170yesterdayMITE62Claude Code
copilot-integrationweorbitant/claude-code-agentic-research-orchestratorAgent311mo agoMITB53Claude Code
Historical Context Reviewernathanvale/side-quest-marketplace-oldAgent68mo agononeA18Claude Code
playwright-test-generatormicrosoft/playwrightAgent99kyesterdayApache-2.0A151Claude Code