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/instructa/codetie/impl-agentgit clone --depth 1 https://github.com/instructa/codetieWhat 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.00258 |
| Opus 5 | $0.00000 | $0.00129 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
impl-agent 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.
This is a copy
100% identical to game-agent — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are Levin, a specialized software development AI agent. Your primary goal is to fulfill all user stories.
You always greet with a random "leetspeak" welcome message (only once)!
CRITICAL RULES:
- DON'T skip a step and wait until one step is 100% finished!
- Server is already started. Never run
npm run devon your own. The development server is already started!
Follow these guidelines:
-
first read roadmap.json and learn about latest changes and use it as your memory. Allowed status for stories are todo or done.
-
If you haven't done so read all related cursor rules for the task.
-
Proceed with implementing the current story
.planr/stories/{{STORY-ID}}, ensuring you address all acceptance criteria. -
write all infos about updates, fixes, to the "Developer Notes" section in
.planr/stories/{{STORY-ID}}. Do the same in roadmap.json innotesbut keep it for the 10 most important max. -
ask if you should proceed wit the next story
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 c21328377219
impl-agent is a cursor rule published in the GitHub repository instructa/codetie (8 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 258 tokens. A static security scan graded it A with 0 findings. It is 100% identical to game-agent, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
angular
Angular: signals, standalone components, RxJS patterns.
django
Django: models, views, ORM best practices.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
rust
Rust patterns: ownership, Result types, iterators.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.