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 skills/gullitmiranda/.cursor/integrationnpx skills add gullitmiranda/.cursor --skill integrationgit clone --depth 1 https://github.com/gullitmiranda/.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/skills/gullitmiranda/.cursor/integration)<a href="https://agentmods.dev/skills/gullitmiranda/.cursor/integration"><img src="https://agentmods.dev/badge/skills/gullitmiranda/.cursor/integration.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.00037 | $0.01156 |
| Opus 5 | $0.00018 | $0.00578 |
| Sonnet 5 | $0.00007 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
integration 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 5d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Rules
Linear Integration
See the linear skill for full Linear rules and CLI commands (skills/linear/).
Quick reference:
- CLI Tool: Linearis (
lineariscommand) - Default Team: Self Driven Platform (PLTFRM)
- Default Status: Backlog
- Issue URLs: Always use full markdown format
GitHub Integration
GitHub CLI Usage
- MANDATORY: Always use GitHub CLI (
gh) for viewing GitHub logs and repository information - Use
ghcommands instead of web interface for log access and repository operations - Prefer
ghCLI over browser-based GitHub operations when possible
Core Commands
gh log- View commit logs and repository historygh pr view- Pull request informationgh issue view- Issue detailsgh repo view- Repository information
GitHub Actions
gh run list- View workflow runsgh run view <run-id>- View specific workflow run detailsgh run logs <run-id>- View workflow logsgh workflow list- List available workflowsgh workflow view <workflow-name>- View workflow detailsgh run watch <run-id>- Watch a workflow run in real-timegh run rerun <run-id>- Rerun failed workflows
Pull Request Management
- Use
.github/pull_request_template.md - Define code ownership rules in
.github/CODEOWNERS - Use consistent labeling system (feat, fix, chore, docs)
- Require appropriate number of reviewers
- Assign reviewers based on code ownership
Trunk Integration
Fix workflow (agent)
When fixing lint/format issues in a Trunk-enabled project: run trunk check --fix first so Trunk auto-fixes what it can; then fix manually whatever remains. Do not skip Trunk—use it first, then the agent.
Tool Configuration
- Prefer configuring tools and linters using their standard configuration files in default paths (e.g.,
.eslintrc,pyproject.toml,.prettierrc) instead of configuring exclusively in.trunk/ - Keep
.trunk/trunk.yamlminimal - use it only for Trunk-specific settings like enabled linters and actions - This ensures tools work consistently whether run via Trunk or directly
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.
- 5d ago First seen · 194 lines · 37 tokens per session scan A 32097d5cf94a
integration is a skill published in the GitHub repository gullitmiranda/.cursor (2 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 1,156 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…