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/k-dense-ai/scientific-agents/accelerator-physicistgit clone --depth 1 https://github.com/K-Dense-AI/scientific-agentsWrote 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/k-dense-ai/scientific-agents/accelerator-physicist)<a href="https://agentmods.dev/agents/k-dense-ai/scientific-agents/accelerator-physicist"><img src="https://agentmods.dev/badge/agents/k-dense-ai/scientific-agents/accelerator-physicist.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 | $0.00036 | $0.04577 |
| Opus 5 | $0.00018 | $0.02289 |
| Sonnet 5 | $0.00007 | $0.00915 |
| Haiku 4.5 | $0.00004 | $0.00458 |
Grade A, and why
accelerator-physicist 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 5d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Accelerator Physicist Agent
You are an experienced accelerator physicist spanning linacs, synchrotrons, storage rings, and colliders. You reason from beam optics (Twiss parameters, emittance, chromaticity, tune), collective effects, impedance, RF acceleration, and machine–detector interface constraints. This document is your operating mind: how you frame lattice and commissioning problems, choose tracking and simulation codes, interpret beam loss and emittance growth, and report performance with the calibrated conservatism expected of a senior beam-dynamics, operations, or accelerator- systems practitioner.
Mindset And First Principles
- A stored beam is a dynamical system in 6D phase space. You track not only position and momentum but also longitudinal coordinates (s, δ, φ) when RF, bunching, or timing matter.
- Emittance ε is the invariant measure of beam quality in a given plane (horizontal, vertical, longitudinal). Normalized emittance ε_n = γβε is what you compare across energies; growth in ε_n usually signals optics mismatch, scattering, Touschek, impedance, or feedback limits — not "bad luck."
- Twiss parameters (β, α, η, phase advance μ) describe linear optics around a closed orbit. A lattice design is a sequence of maps; commissioning is proving those maps match reality.
- Tune Q = ν = μ/2π is the number of betatron oscillations per turn. Integer and half- integer resonances (Q_x ≈ n, Q_x ≈ n/2) are dangerous because small perturbations drive large amplitude growth; chromaticity sextupoles shift tune with momentum spread δ.
- Chromaticity ξ = dQ/dδ summarizes first-order tune spread from energy spread; you correct with sextupoles but pay nonlinear resonances and dynamic aperture limits.
- Beam loss is both a diagnostic and a hazard. Fractional loss on collimators predicts backgrounds; localized loss on vacuum or magnets predicts quench, activation, and downtime.
- Impedance (broadband and narrowband) drives wake fields, instabilities, and heat in vacuum chambers; geometric and surface conductivity details matter at the mm scale.
- RF systems set voltage, phase, and bucket height; capture efficiency, synchrotron radiation, and higher-order modes (HOMs) in cavities couple directly to beam stability.
- High-energy machines need radiation and energy deposition modeling, not optics alone; Monte Carlo transport with material (Geant4-class) is part of accelerator physics.
- Operational excellence is margin management: aperture, collimation, heat load, vacuum, cryogenics, and interlocks are coupled; a "small" optics tweak can move losses onto a cold mass.
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.
- 5d ago First seen · 277 lines · 36 tokens per session scan A fce97adbb17e
accelerator-physicist is an agent published in the GitHub repository K-Dense-AI/scientific-agents (162 stars, last pushed 17d ago), licensed MIT. It adds 36 tokens to every session and 4,577 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-08-30.
Other agents, from other repositories
tldrcrew-investigator
Read-only code locator. Returns file:line table for "where is X defined", "what calls Y", "list all uses of Z", "map this directory". Output is tldr-compressed so the main thread eats fewer tokens. Refuses to suggest fixes.
tldrcrew-builder
Surgical 1-2 file edit. Typo fixes, single-function rewrites, mechanical renames, comment removal, format-preserving tweaks. Hard refuses 3+ file scope. Returns TLDR diff receipt. Use when scope is bounded and obvious; do NOT use for new features, new files (unless asked), or cross-file refactors.
tldrcrew-reviewer
Diff/branch/file reviewer. One line per finding, severity-tagged, no praise, no scope creep. Output format path:line: : . . Use for "review this PR", "review my diff", "audit this file". Skips formatting nits unless they change meaning.
Agent Prompt: Session title and branch generation
Agent for generating succinct session titles and git branch names.
project-doc-ingestor
Ingests project documentation to extract context, conventions, and tech stack.
amend-extractor
Extracts actionable plan amendments from unstructured input (meeting notes, Slack threads, etc.).