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/DayronDLR/sap-enterprise-stack-pluginWrote 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/commands/dayrondlr/sap-enterprise-stack-plugin/sap-techlead)<a href="https://agentmods.dev/commands/dayrondlr/sap-enterprise-stack-plugin/sap-techlead"><img src="https://agentmods.dev/badge/commands/dayrondlr/sap-enterprise-stack-plugin/sap-techlead/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/commands/dayrondlr/sap-enterprise-stack-plugin/sap-techlead"><img src="https://agentmods.dev/badge/commands/dayrondlr/sap-enterprise-stack-plugin/sap-techlead.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.00026 | $0.03528 |
| Opus 5.5 | $0.00010 | $0.01411 |
| Sonnet 5.5 | $0.00005 | $0.00706 |
| Haiku 4.5 | $0.00003 | $0.00353 |
Grade A, and why
sap-techlead 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 22d 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 GPL-3.0
The repository is licensed GPL-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.
- 22d ago Changed · +5 lines 2899dc33aebe
- 25d ago Changed · +7 lines 53abb59761db
- 26d ago Changed · +22 lines 78d8e439b87a
- 1mo ago Changed · +1 lines 0dcd9440344a
- 1mo ago Changed · +51 lines bae9de7eb62b
- 1mo ago Changed · +1 lines · +26 tokens per session ccb41bcd07bf
- 1mo ago Changed · +1 lines fa02ca124ef7
- 1mo ago Changed 3597174a939c
- 1mo ago First seen · 211 lines · 0 tokens per session scan A e0f763045fd5
sap-techlead is a command published in the GitHub repository DayronDLR/sap-enterprise-stack-plugin (5 stars, last pushed 21d ago), licensed GPL-3.0. It adds 26 tokens to every session and 3,528 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.