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/gabriel-romero-poza/synapse-mcpWrote 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/gabriel-romero-poza/synapse-mcp/agentic-workflow)<a href="https://agentmods.dev/rules/gabriel-romero-poza/synapse-mcp/agentic-workflow"><img src="https://agentmods.dev/badge/rules/gabriel-romero-poza/synapse-mcp/agentic-workflow.svg" alt="Measured on agentmods" 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.00298 | $0.00298 |
| Opus 5 | $0.00149 | $0.00149 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
agentic-workflow 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 7d 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
Agentic workflow
Before making changes in this repo, follow this workflow.
1. Read context
- AGENTS.md — project purpose, stack, and current phase.
- docs/ — vision, architecture, and any design notes.
- .cursor/rules/ — commit format, TypeScript rules, and other guardrails.
- CONTRIBUTING.md — commit conventions, PR process, and code standards.
This reduces hallucinations and keeps edits aligned with the project.
2. Scope and commits
- One logical change per commit. Use Conventional Commits (see commits rule).
- Prefer small, reviewable edits over one large “do everything” change.
- If the user’s request is vague, break it into clear steps and confirm if needed.
3. When in doubt, ask
- Ambiguous requirements, conflicting instructions, or changes that would remove or bypass guardrails (e.g. CONTRIBUTING, AGENTS.md, rules): ask the user instead of guessing.
- Do not remove or weaken AGENTS.md, CONTRIBUTING.md, or .cursor/rules unless the user explicitly requests it.
4. After editing
- Ensure the project still builds (
pnpm run build). - Propose commit message(s) that follow the commit rule.
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.
- 7d ago First seen · 34 lines · 298 tokens per session scan A 06f9a0527c91
agentic-workflow is a cursor rule published in the GitHub repository gabriel-romero-poza/synapse-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 298 tokens to every session, about $0.0015 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.