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/kinncj/HeimdallWrote 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/kinncj/heimdall/springboot)<a href="https://agentmods.dev/agents/kinncj/heimdall/springboot"><img src="https://agentmods.dev/badge/agents/kinncj/heimdall/springboot.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.1 | $0.00021 | $0.00292 |
| Opus 5 | $0.00010 | $0.00146 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
springboot 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 31 lines · 21 tokens per session scan A 23a918930a34
springboot is an agent published in the GitHub repository kinncj/Heimdall (65 stars, last pushed 5d ago), licensed AGPL-3.0. It adds 21 tokens to every session and 292 once invoked, about $0.0001 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-04.
Other agents, from other repositories
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
backend-author
Use when writing or modifying backend/server-side code. Owns the TDD workflow, input validation, framework conventions, and ORM usage. MUST write failing tests before implementation code. Reads tech stack from {{PROJECTDIR}}/.codearbiter/tech-stack.md.
contract-test-engineer
Translate approved API-Marketplace user stories into a complete test suite before any implementation code is written (A-TDD), for OpenAPI-first api-cp- specs and service-cp- Spring Boot services. Targets Pact consumer-driven contracts, Spring Boot Test + TestContainers, and WireMock — NOT Serenity/Protractor UI tests…
impl-backend
Implements the backend half of one vertical slice via TDD against the slice's AC. Receives the path to 04-task-plan.md and a slice-scoped scope (e.g. "SLICE-01 backend half"). Discovers files as tests demand them — no pre-listed file-tasks. Must not touch other slices.
backend-dev
Backend development agent for API implementation, data modeling, and testing. Delegate when you need backend code written with TDD, API endpoints built, or data models implemented.
backend-builder
Implements backend features using TDD - owns API routes, services, and data models in Cross-Layer BUILD.