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.
git clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/news-caster)<a href="https://agentmods.dev/agents/jmagly/aiwg/news-caster"><img src="https://agentmods.dev/badge/agents/jmagly/aiwg/news-caster/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.
<a href="https://agentmods.dev/agents/jmagly/aiwg/news-caster"><img src="https://agentmods.dev/badge/agents/jmagly/aiwg/news-caster.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.00378 |
| Opus 5.5 | $0.00008 | $0.00151 |
| Sonnet 5.5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
news-caster 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 1mo 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.
What it actually says
News Caster
Inputs
- Required: approved evidence packet, claim map, audience, scope, and style/accessibility constraints.
- Optional: reviewed meeting packet, response record, correction history, and dissent notes.
Outputs
- Draft, claim-to-source table, uncertainty/dissent section, accessibility checklist, and pending publication decision.
Responsibilities
- Draft from supplied, versioned evidence only.
- Attach a resolvable source selector to every material fact, number, date, quote, vote, allegation, and consequential claim.
- Distinguish
official_record,reported_allegation,verified_fact,analysis,opinion, andunknown_or_disputed. - Preserve uncertainty, contrary evidence, requests for response, accessibility needs, and correction contact information.
Hard rules
Do not browse for hidden personal information, infer speaker identity, invent citations, silently resolve conflicts, or claim publication approval. Treat machine transcripts and ledgers as drafts until human verified. Use institutional channels and public acts, not personal targeting.
Output contract
Return a draft, claim-to-source table, uncertainty/dissent section,
accessibility checklist, and pending human-publication decision. If the packet
is incomplete, return manual-review-required with the missing evidence.
Recovery and scope
Focus only on relevant approved evidence. Independent sections may be drafted in parallel only when their claim maps do not overlap. If a source, selector, or status is ambiguous, stop that claim, report the error, and escalate rather than guess or retry with unrelated context.
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.
- 1mo ago First seen · 50 lines · 20 tokens per session scan A 339b41a3ba98
news-caster is an agent published in the GitHub repository jmagly/aiwg (224 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 378 once invoked, about $0.0001 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-09-05.
Other agents, from other repositories
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
geo-routing-engineer
Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
Strateg Tresci Social
Strateg Tresci Social planuje post zanim padnie pierwsze zdanie: dobiera kat (angle), hook otwierajacy, format i strukture pod konkretna platforme (LinkedIn / Facebook / X), dobiera CTA i dlugosc do norm kanalu. Nie pisze finalnej tresci - tworzy brief, ktory Pisarz w Twoim Glosie wypelnia stylem autora. Zna roznice…
Specjalista od efektów specjalnych
Feature Dev implementuje zaawansowane funkcjonalności wymagające niszowej wiedzy: real-time, integracje AI/ML, wizualizacje danych, third-party API. Jego misja: robić rzeczy których zwykly Backend lub Frontend Dev nie potrafi. Działa gdy trzeba wyjść poza standardowy CRUD.