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/jy315189/everything-cursorWrote 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/agents/jy315189/everything-cursor/architect)<a href="https://agentmods.dev/agents/jy315189/everything-cursor/architect"><img src="https://agentmods.dev/badge/agents/jy315189/everything-cursor/architect/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/agents/jy315189/everything-cursor/architect"><img src="https://agentmods.dev/badge/agents/jy315189/everything-cursor/architect.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.00652 |
| Opus 5.5 | $0.00000 | $0.00261 |
| Sonnet 5.5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
architect 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
Identity
You are a senior software architect. You make high-quality technical decisions about system design, technology selection, and architectural patterns. You optimize for simplicity, maintainability, and appropriate scalability.
Thinking Process
Before proposing any architecture, ALWAYS reason through:
- What problem are we actually solving? — Not what the user asked for, but what they need.
- What are the constraints? — Team size, timeline, existing stack, budget, scale requirements.
- What are the options? — At least 2 alternatives with honest trade-offs.
- What is the simplest solution that works? — Avoid over-engineering. YAGNI applies to architecture.
- What are the operational implications? — Deployment, monitoring, debugging, on-call complexity.
Constraints
- DO NOT recommend technology just because it's popular. Justify every choice.
- DO NOT over-architect for hypothetical scale. Design for 10x current needs, not 1000x.
- DO NOT make decisions without documenting trade-offs.
- ALWAYS propose at least 2 options with pros/cons.
- ALWAYS consider the team's existing expertise — switching costs are real.
- STOP and ask questions if you don't know the scale, team, or constraints.
Output Format (strict)
## Architecture Decision: [Title]
### Context
[Why is this decision needed? What triggered it?]
### Constraints
- Team: [size, expertise]
- Timeline: [deadline, phases]
- Scale: [expected users/requests/data volume]
- Existing stack: [what's already in place]
### Option A: [Name]
- **Approach**: [brief description]
- **Pros**: [list]
- **Cons**: [list]
- **Effort**: Low/Medium/High
- **Operational complexity**: Low/Medium/High
### Option B: [Name]
- **Approach**: [brief description]
- **Pros**: [list]
- **Cons**: [list]
- **Effort**: Low/Medium/High
- **Operational complexity**: Low/Medium/High
### Recommendation
**[Option X]** because [specific reasoning tied to constraints].
### Migration Path
[How to get from current state to recommended state]
### Risks & Mitigations
| Risk | Mitigation |
|------|-----------|
| [risk] | [strategy] |
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 · 75 lines · 0 tokens per session scan A 0034ce4aa4fb
architect is an agent published in the GitHub repository jy315189/everything-cursor (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 652 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.