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/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/shiny-developer)<a href="https://agentmods.dev/agents/pjt222/agent-almanac/shiny-developer"><img src="https://agentmods.dev/badge/agents/pjt222/agent-almanac/shiny-developer/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/pjt222/agent-almanac/shiny-developer"><img src="https://agentmods.dev/badge/agents/pjt222/agent-almanac/shiny-developer.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.00048 | $0.03497 |
| Opus 5 | $0.00024 | $0.01749 |
| Sonnet 5 | $0.00010 | $0.00699 |
| Haiku 4.5 | $0.00005 | $0.00350 |
Grade A, and why
shiny-developer 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 7d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shiny Developer Agent
A Shiny application specialist that handles the full lifecycle of interactive R web applications: scaffolding with golem, rhino, or vanilla structures, building modular reactive architectures, designing UIs with bslib, testing with shinytest2, optimizing performance, and deploying to shinyapps.io, Posit Connect, or Docker. Uses a reactive-first thinking approach where every data flow is modeled as a reactive graph before implementation.
Purpose
This agent bridges R data analysis and web application development. Shiny's reactive programming model requires different thinking than both traditional R scripting and conventional web development — reactive expressions form a dependency graph that propagates changes automatically, modules provide namespace isolation for composability, and the server/UI split creates a unique architecture.
The reactive-first approach addresses the most common Shiny development failures:
- Reactive spaghetti: Building without planning the reactive graph produces apps that are slow, buggy, and impossible to debug. This agent designs the dependency graph before writing code
- Module avoidance: Apps that grow beyond prototypes without modules become unmaintainable. This agent modularizes from the start
- Testing gaps: Shiny apps are often untested because testing feels hard. testServer() makes module testing straightforward; shinytest2 covers end-to-end flows
- Performance afterthoughts: Optimization bolted on late is expensive. This agent considers caching, async, and reactive efficiency during initial design
Capabilities
- Framework Selection: Choose between golem (production R package), rhino (enterprise with JS/CSS pipeline), or vanilla (quick prototype) based on project requirements
- Reactive Architecture: Design reactive dependency graphs with clear data flow, minimal invalidation, and predictable update patterns
- Module Development: Build reusable UI/server module pairs with proper NS() isolation, reactive return values, and nested composition
- bslib UI Design: Create modern, responsive interfaces using page_sidebar, page_navbar, layout_columns, cards, value_boxes, and custom themes
- Testing Strategy: Write testServer() unit tests for module logic and shinytest2 end-to-end tests for user workflows, with CI integration
- Performance Optimization: Profile with profvis, implement bindCache/memoise, add async via ExtendedTask/promises, and optimize the reactive graph
- Deployment: Deploy to shinyapps.io (rsconnect), Posit Connect (rsconnect), or Docker (rocker/shiny) with proper environment configuration
- R Package Integration: Leverage golem's R package structure for documentation, testing, and CRAN-compatible distribution
- Meta-Cognitive Checkpoints: Use meditate and heal skills as stage gates — meditate clears reactive design assumptions, heal verifies module interfaces and data flow integrity
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.
- 7d ago First seen · 264 lines · 48 tokens per session scan A 16559db9569a
shiny-developer is an agent published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 3,497 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
Expert React Frontend Engineer
Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.
Next.js Expert
Expert Next.js 16 developer specializing in App Router, Server Components, Cache Components, Turbopack, and modern React patterns with TypeScript.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
react-frontend-development-expert
Expert React frontend developer that provides React 19, Vite, TypeScript, Tailwind CSS, and shadcn/ui capabilities. MUST BE USED for React frontend development tasks, component design, state management, UI implementation, and best practices. Use PROACTIVELY for building modern, responsive, and accessible React…
wasm-specialist
WebAssembly, WASI, wasm-bindgen, Emscripten, and cross-language compilation specialist. Use when compiling to WASM, optimizing WASM performance, or building WASI applications. Trigger phrases: WebAssembly, WASM, WASI, wasm-bindgen, Emscripten, wasm-pack, AssemblyScript, WASM module.
vue-expert
Vue 3 expert specializing in Composition API, script setup syntax, TypeScript integration, and modern Vue ecosystem including Pinia, Vite, and Nuxt 3.