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/yu-iskw/coding-agent-fabric/tech-stackgit clone --depth 1 https://github.com/yu-iskw/coding-agent-fabricWhat 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.00317 | $0.00317 |
| Opus 5 | $0.00159 | $0.00159 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
tech-stack 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.
What it actually says
Tech Stack
This project uses:
- Package Manager: pnpm
- Node.js Version: (read from .node-version)
pnpm Workspace & Monorepo Best Practices
This repository is structured as a pnpm workspace (see pnpm-workspace.yaml).
Common Commands
- Install All Dependencies:
pnpm install - Add Dependency:
- To current package:
pnpm add <pkg> - As dev dependency:
pnpm add -D <pkg> - To workspace root:
pnpm add -w <pkg>
- To current package:
- Run Scripts:
- In current package:
pnpm <script>(e.g.,pnpm test) - In all packages:
pnpm -r <script> - In specific package:
pnpm --filter <pkg-name> <script>
- In current package:
Workspace Protocol
Always use the workspace: protocol when referencing local packages in package.json:
{
"dependencies": {
"@my-project/common": "workspace:*"
}
}
Dependency Management
pnpm uses a content-addressable store and a non-flat node_modules structure. This ensures:
- Strictness: You cannot access dependencies that are not explicitly declared in your
package.json. - Efficiency: Disk space is saved by sharing package files across projects.
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 · 45 lines · 317 tokens per session scan A 5a7eb82b7d16
tech-stack is a cursor rule published in the GitHub repository yu-iskw/coding-agent-fabric (1 stars, last pushed 16d ago), licensed Apache-2.0. It adds 317 tokens to every session, about $0.0016 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 cursor rules, from other repositories
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
new_features
Guidelines for integrating new features into the Task Master CLI.
utilities
// ✅ DO: Create focused, reusable utilities /.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.
commands
Guidelines for implementing CLI commands using Commander.js.
git_workflow
Git workflow integrated with Task Master for feature development and collaboration.