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/jkudjo/oh-my-cursor/explorenpx skills add Jkudjo/oh-my-cursor --skill exploregit clone --depth 1 https://github.com/Jkudjo/oh-my-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/jkudjo/oh-my-cursor/explore)<a href="https://agentmods.dev/skills/jkudjo/oh-my-cursor/explore"><img src="https://agentmods.dev/badge/skills/jkudjo/oh-my-cursor/explore.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.00020 | $0.00303 |
| Opus 5 | $0.00010 | $0.00151 |
| Sonnet 5 | $0.00004 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
explore 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.
What it actually says
explore
Invoke this skill to understand a codebase or subsystem before making changes.
When to use
- Starting work in an unfamiliar part of the codebase
- Before designing a plan that touches multiple files
- When you need to understand data flow, entry points, or conventions
What it does
- No code changes — read-only throughout
- Maps the relevant subsystem:
- Entry points and main files
- Data flow and call graph
- Key types and interfaces
- External dependencies
- Conventions and patterns in use
- Produces an Exploration Report:
## Exploration: <topic> ### Files - `path/to/file.ts` — role and responsibility ### Data flow [description of how data moves] ### Conventions [naming, patterns, idioms in use] ### Key decisions [non-obvious design choices] ### Entry points for changes [where to start if you need to modify this] - Saves report to memory key
explore-<topic>
Example
@explore "how the authentication middleware works"
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 · 52 lines · 20 tokens per session scan A 0c71373422db
explore is a skill published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 303 once invoked, about $0.0001 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
Release Notes Generation
Mandatory fast-mcp-telegram release workflow. Use when the user says release, merge and release, bump version, tag, gh release, PyPI publish, or Telegram version announcement.
feature-development
Feature development workflow for Telegram MCP projects. Use when implementing new features including research, planning, implementation, testing, and documentation.
sourcery-pr-cycle
Runs the PR creation and Sourcery AI review loop until merge-ready: open PR with gh, poll checks and comments, fix blocking issues, push, re-request review, repeat. Use when the user asks to create a PR, run the Sourcery cycle, address Sourcery review comments, or get a branch merge-ready after review.
telegram-patterns
Telegram-specific patterns and Telethon library usage.
Clean Up Docs Push
Code cleanup, docs update, and git push workflow.
Remove Old Logs
Remove log files older than 1 day from logs directory.