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/magarcia/mcp-server-giphy/cursorrulesgit clone --depth 1 https://github.com/magarcia/mcp-server-giphyWrote 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/magarcia/mcp-server-giphy/cursorrules)<a href="https://agentmods.dev/rules/magarcia/mcp-server-giphy/cursorrules"><img src="https://agentmods.dev/badge/rules/magarcia/mcp-server-giphy/cursorrules.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 | $0.00660 | $0.00660 |
| Opus 5 | $0.00330 | $0.00330 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
cursorrules 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cursorrules — 89% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in TypeScript, Node.js, and RESTful API development. This project is a GIPHY API client library.
TypeScript Standards
- Use TypeScript for all new code; avoid any
anytypes - Prefer interfaces over types for API response objects
- Use type predicates and guards to handle nullable values rather than type assertions
- Export well-defined response types for all API endpoints
- Use descriptive variable names that reflect the GIPHY API terminology
Code Structure
- Keep files focused on a single responsibility
- Separate API endpoint functions by category (search, trending, random, etc.)
- Use async/await for all API requests, not Promises with .then()
- Handle rate limiting and error responses consistently
- Include JSDoc comments for all public methods and interfaces
API Client Design
- Ensure all API endpoints support the full range of parameters from GIPHY API
- Include proper pagination support for endpoints that return multiple results
- Use reasonable defaults for optional parameters
- Make the client configurable with options like rating, language, etc.
- Implement proper error handling with custom error types
Testing Standards
- Write unit tests for all API endpoint functions
- Use mocks for external API calls in tests
- Include integration tests that validate against real API responses
- Test error handling scenarios like rate limiting and invalid API keys
- Ensure all public interfaces have test coverage
Performance Considerations
- Implement request caching where appropriate
- Support both ESM and CommonJS module formats
- Keep dependencies minimal and up-to-date
- Ensure the package has a small bundle size
- Support tree-shaking for modular imports
Documentation
- Keep README examples up-to-date with the current API
- Include TypeDoc documentation for all public interfaces
- Document rate limiting considerations
- Provide usage examples for each API endpoint category
- Include sample response objects in documentation
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.
- 4d ago First seen · 90 lines · 660 tokens per session scan A 950787eeecf0
cursorrules is a cursor rule published in the GitHub repository magarcia/mcp-server-giphy (33 stars, last pushed 1y ago), licensed MIT. It adds 660 tokens to every session, about $0.0033 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-30.
Other cursor rules, from other repositories
code-style
TypeScript style, language policy, hygiene, shared domain vocabulary.
cursorrules
When the user asks about lead scoring, use lead-scoring-ai-mcp tools: scorelead, addlead, updateleadactivity, getleadscore, getallleads.
cursorrules
When the user asks about web research, use web-research-mcp tools: websearch, browsepage, extractarticle, researchtopic, getweather.
cursorrules
When the user asks about nist rmf, use nist-rmf-ai-mcp tools: assessriskprofile, mapaiimpact, generateriskcontrols, crosswalktoeuaiact, createriskreport.
cursorrules
When the user asks about quiz generator, use quiz-generator-ai-mcp tools: generatequiz, validateanswers, generateflashcards, assessdifficulty.
cursorrules
When the user asks about social media, use social-media-ai-mcp tools: schedulepost, generatehashtags, analyzeengagement, plancontentcalendar, getaudienceinsights.