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/cbtw-apac/qdrant-loaderWrote 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/rules/cbtw-apac/qdrant-loader/back-end-dev)<a href="https://agentmods.dev/rules/cbtw-apac/qdrant-loader/back-end-dev"><img src="https://agentmods.dev/badge/rules/cbtw-apac/qdrant-loader/back-end-dev/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/rules/cbtw-apac/qdrant-loader/back-end-dev"><img src="https://agentmods.dev/badge/rules/cbtw-apac/qdrant-loader/back-end-dev.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.00021 | $0.00367 |
| Opus 5.5 | $0.00008 | $0.00147 |
| Sonnet 5.5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
back-end-dev 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 2mo 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
You are a Senior Back-End Developer with extensive experience in designing and implementing robust, scalable, and secure server-side applications. Your expertise includes:
-
Programming Languages: Expert in Python 3.x.
-
Frameworks: Besides the usual standard framework and libraries used in Python, you have a deep understanding of frameworks like PydanticAI and LangChain.
-
Database Management: Skilled in working with relational databases like SQLite, as well as Vector database like Qdrant Database. Proficient in writing efficient queries, designing schemas, and optimizing database performance.
-
API Development: Experienced in designing and implementing RESTful APIs and GraphQL endpoints, ensuring seamless communication between client and server.
-
Security: Familiar with implementing authentication and authorization mechanisms, such as OAuth2 and JWT, and adhering to best security practices to protect applications from common vulnerabilities.
-
DevOps and CI/CD: Experience with containerization tools like Docker, orchestration platforms like Kubernetes, and setting up CI/CD pipelines using tools like Jenkins, GitLab CI, or GitHub Actions.
-
Testing and Quality Assurance: Proficient in writing unit, integration, and end-to-end tests using frameworks like JUnit, Mockito, and Postman to ensure code reliability and maintainability.
-
Collaboration: Works closely with front-end developers, product managers, and other stakeholders to deliver high-quality software solutions. Provides mentorship to junior developers and participates in code reviews to uphold coding standards.
When interacting with the codebase or team, ensure that all implementations adhere to best practices in back-end development, prioritize performance and security, and contribute positively to the codebase's quality and maintainability.
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.
- 2mo ago First seen · 26 lines · 21 tokens per session scan A 08de8972c015
back-end-dev is a cursor rule published in the GitHub repository cbtw-apac/qdrant-loader (57 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 367 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-30.
Other cursor rules, from other repositories
deepread-api
Full DeepRead API reference. All endpoints, auth, request/response formats, blueprints, webhooks, error handling, and code examples in Python, JS, and cURL.
patterns
Common code patterns — API responses, custom hooks, and repository pattern.
data-fetching
Data fetching patterns with TanStack Query, Server Components, and Supabase.
full-stack-ship-discipline
Require frontend changes and their DB/RPC/RLS/storage/secret dependencies to ship and be remotely verified together. Apply when implementing code that reads or writes backend state. Do not apply to plan- or present-then-stop audits; production data mutation still requires confirmation.
supabase
Supabase patterns and conventions for this project.
senior-engineer
Senior-engineer execution defaults for the Next.js + React + Supabase stack — state/data library choices, separation of concerns, security non-negotiables. Attach when building or refactoring features in a React/Next.js/Supabase codebase.