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/bekirdag/tnl-intelligenceWrote 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/bekirdag/tnl-intelligence/tnl-what-changed)<a href="https://agentmods.dev/commands/bekirdag/tnl-intelligence/tnl-what-changed"><img src="https://agentmods.dev/badge/commands/bekirdag/tnl-intelligence/tnl-what-changed.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.00012 | $0.00087 |
| Opus 5 | $0.00006 | $0.00044 |
| Sonnet 5 | $0.00002 | $0.00017 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
tnl-what-changed 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 6d 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.
What it actually says
Use the tnl_research_what_changed MCP tool for this request. Require or visibly resolve the time window, preserve the returned as-of timestamp, classifications, unknowns, citations, and TNL Bot attribution. Do not execute trades or present the result as investment advice. If no question is selected, ask only for the missing research question.
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.
- 6d ago First seen · 6 lines · 12 tokens per session scan A b47cc2424c4a
tnl-what-changed is a command published in the GitHub repository bekirdag/tnl-intelligence (2 stars, last pushed 29d ago), licensed MIT. It adds 12 tokens to every session and 87 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-08-31.
Other commands, from other repositories
potpie-record
Record durable Potpie learnings after useful work.
potpie-feature
Use Potpie context before feature work. Load potpie-project-preferences first, and load potpie-infra-architecture when the change touches services, deployment, adapters, or runtime behavior.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).