Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/CharLEE-X/effect-cursor-rulesnpx agentmods add rules/charlee-x/effect-cursor-rules/ai-tools-maintenanceWrote 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/charlee-x/effect-cursor-rules/ai-tools-maintenance)<a href="https://agentmods.dev/rules/charlee-x/effect-cursor-rules/ai-tools-maintenance"><img src="https://agentmods.dev/badge/rules/charlee-x/effect-cursor-rules/ai-tools-maintenance/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/charlee-x/effect-cursor-rules/ai-tools-maintenance"><img src="https://agentmods.dev/badge/rules/charlee-x/effect-cursor-rules/ai-tools-maintenance.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.00000 | $0.02195 |
| Opus 5.5 | $0.00000 | $0.00878 |
| Sonnet 5.5 | $0.00000 | $0.00439 |
| Haiku 4.5 | $0.00000 | $0.00219 |
Grade A, and why
ai-tools-maintenance 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.
How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Tools Maintenance Rule
AI Assistant Authority
As the AI assistant, I have the authority and responsibility to automatically maintain AI tools in sync with the BlogPostService when I detect changes that would make the tools outdated or incomplete.
When to Update AI Tools
Automatic Updates Should Occur When:
-
New BlogPostService Methods Added
- New public methods in
blog.api-client.ts - New API endpoints that should be exposed as tools
- New functionality that would benefit AI agents
- New public methods in
-
Method Signatures Changed
- Parameter types modified
- Return types updated
- Input/output schemas changed
-
Method Removed or Deprecated
- Methods no longer available in BlogPostService
- Deprecated endpoints that should be removed
-
Schema Updates
- New input/output types in blog-domain
- Updated validation requirements
- New branded types or constraints
AI Tool Structure Pattern
Standard Tool Template
Every AI tool MUST follow this exact pattern:
import { /* Required types */ } from '@t6c/blog-domain' // or '@t6c/domain-common'
import { AiTool, ToolError } from '@t6c/lib-ai'
import { Effect, String as S, Schema } from 'effect'
import { BlogPostService } from '../blog/index.js'
const tool = AiTool.make('ToolNameTool', {
success: Schema.String,
failure: ToolError,
parameters: Schema.Struct({
// Define parameters based on method signature
}).fields,
description: S.stripMargin(`
| Clear description of what the tool does.
| Include parameter explanations if complex.
| Mention return value format.
`),
})
const handler = ({
// Parameters matching the schema
}: {
// TypeScript types for parameters
}): Effect.Effect<string> =>
Effect.gen(function* () {
const blogPostService = yield* BlogPostService
const result = yield* blogPostService.methodName(/* parameters */)
return `Success message: ${JSON.stringify(result)}`
}).pipe(
Effect.catchAll((e) =>
Effect.succeed(`Error message with context: ${e}`),
),
Effect.provide(BlogPostService.Default),
)
export const ToolName = {
tool,
handler,
}
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 · 292 lines · 2,195 tokens per session scan A ca8e07cfe31a
ai-tools-maintenance is a cursor rule published in the GitHub repository CharLEE-X/effect-cursor-rules (6 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,195 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-31.
Other cursor rules, from other repositories
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
server-state
USE WHEN: Fetching and caching server data with TanStack Query 5: queryOptions, hooks, mutations, invalidation.
selectools-providers
Rules for working with LLM provider adapters in selectools.