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 rules/dpro-at/tel-agent/python-agent-apigit clone --depth 1 https://github.com/Dpro-at/Tel-AgentWhat 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.00000 | $0.00227 |
| Opus 5 | $0.00000 | $0.00113 |
| Sonnet 5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
python-agent-api 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 yesterday.
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.
- yesterday First seen · 25 lines · 0 tokens per session scan A 4fda5f7c33d3
python-agent-api is a cursor rule published in the GitHub repository Dpro-at/Tel-Agent (44 stars, last pushed yesterday), licensed AGPL-3.0. It costs nothing until one of its globs matches a file; then it loads 227 tokens. 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 cursor rules, from other repositories
agent-development
Python agents are typically in folders named agent-py/ or agent/ and use the sdk-python/ package.
statusline
Turn the usage statusLine on or off (model + context% + 5-hour usage% in every project) without editing config by hand. Runs bin/install-statusline.sh, which installs the script to /.claude and merges the setting without clobbering other keys. Opt-in, global, run once per machine; /statusline off disables it.
add-linter
Add linter configs and GitHub Actions workflows for languages detected in the current repo. Use when the user wants to add linters, set up code quality checks, or after sync-scaffold suggests running /add-linter.
simplify
Structural-quality review of changed code — score against the four-dimension rubric, gate at 10/10, and (in auto-fix mode or with --fix) apply reuse/simplification/efficiency/altitude cleanups. Includes a diff-economy lens; correctness is /validate, full-repo survey is /audit.
create-pr
Create a pull request for the current branch and immediately subscribe to PR activity. Use when the user wants to open a PR, submit changes for review, or push and create a pull request.
conventional-commits
Always use Conventional Commits for git commit messages.