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/databayt/hogwartsWrote 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/databayt/hogwarts/workflow)<a href="https://agentmods.dev/agents/databayt/hogwarts/workflow"><img src="https://agentmods.dev/badge/agents/databayt/hogwarts/workflow/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/databayt/hogwarts/workflow"><img src="https://agentmods.dev/badge/agents/databayt/hogwarts/workflow.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.00014 | $0.04111 |
| Opus 5.5 | $0.00006 | $0.01644 |
| Sonnet 5.5 | $0.00003 | $0.00822 |
| Haiku 4.5 | $0.00001 | $0.00411 |
Grade A, and why
workflow 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 664 lines · 14 tokens per session scan A 0f26aef8c55f
workflow is an agent published in the GitHub repository databayt/hogwarts (18 stars, last pushed yesterday), with no licence file. It adds 14 tokens to every session and 4,111 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-01.
Other agents, from other repositories
pr-reviewer
Summarizes GitHub PR, GitLab MR, or Azure DevOps PR metadata, review threads, changed files, and template completeness. Use during review-ticket or code-review workflows when PR/MR context exists.
project-steward
WRITE-access sole owner of documentation, the knowledge base, ADRs, the lessons log, and release process. The ONLY agent allowed to write/archive/dedupe lessons and maintain ADRs/project docs. Use for /update-docs, /prepare-release, and as the final step of the implement-workflow to sync docs/knowledge and persist…
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.
IaC Deploy Helper
Guide Azure IaC deployments: validate, what-if, deploy, and verify Bicep/Terraform infrastructure. Use when deploying or troubleshooting.
IaC Security Reviewer
Security review for Azure IaC: secrets exposure, managed identity, RBAC, network isolation, Key Vault hardening, OWASP cloud top 10.
Bicep Reviewer
Review Bicep templates for best practices: naming, parameters, security, module structure, linter violations, API versions.