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 skills add markus-global/markus --skill markus-hub-connectorgit clone --depth 1 https://github.com/markus-global/markusWrote 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/markus-global/markus/markus-hub-connector)<a href="https://agentmods.dev/skills/markus-global/markus/markus-hub-connector"><img src="https://agentmods.dev/badge/skills/markus-global/markus/markus-hub-connector.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.00604 |
| Opus 5 | $0.00010 | $0.00302 |
| Sonnet 5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
markus-hub-connector 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 8d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markus Hub Connector
You have access to the Markus Hub community marketplace via MCP tools (prefixed markus-hub__).
This lets you search for shared packages, download them locally, publish user creations, and manage published items.
When to use these tools
Use Hub tools when the user wants to:
- Find agents, teams, or skills shared by the community
- Download a package from Hub to try locally
- Share/publish a builder artifact to Hub
- Check what they've published on Hub
Do NOT use these tools for local skill/agent management — those are separate operations.
Authentication
Hub operations that modify data (download, publish, my_items) require the user to be logged in to Markus Hub via the web UI. If a tool returns an authentication error, tell the user to log in to Hub from the Markus web interface first.
The login state is synced automatically — no manual token setup is needed.
Tool reference
| Tool | Purpose | Auth required |
|---|---|---|
markus-hub__hub_search |
Search Hub for packages by keyword, type, category | No |
markus-hub__hub_download |
Download a package to local builder-artifacts | Yes |
markus-hub__hub_publish |
Publish a local artifact to Hub | Yes |
markus-hub__hub_my_items |
List the user's published items | Yes |
Common workflows
Finding and downloading a skill
1. markus-hub__hub_search → query="code review", type="skill"
2. Review results, confirm with user which one to download
3. markus-hub__hub_download → id="<item_id>"
4. Tell user to install from Builder page
Publishing a builder artifact
1. markus-hub__hub_publish → directory="~/.markus/builder-artifacts/skills/my-skill"
(auto-reads manifest + files from directory)
2. Share the Hub URL with the user
Checking published items
1. markus-hub__hub_my_items → see all published packages
2. Report status to user
Best practices
- Always confirm before publishing: Show the user what will be published (name, description, files) before calling
hub_publish. - Use directory mode for publish: When publishing a local artifact, pass the
directoryparameter — it auto-reads the manifest and all files. - Guide on auth errors: If a tool returns an auth error, tell the user to log in via the Hub icon in the Markus web UI.
- Search before download: Help the user find the right package before downloading.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 65 lines · 21 tokens per session scan A d8ad1f8cddac
markus-hub-connector is a skill published in the GitHub repository markus-global/markus (160 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 604 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-30.
Other skills, from other repositories
openai-whisper-api
Transcribe audio via OpenAI Audio Transcriptions API (Whisper).
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
seo-crawl
Agent-wide core connector rule: when any connected search console is used, discover its operations with listconnectortools and invoke each selected operation through callconnectortool; naming listsites or an analytics operation without the core invocation is not execution.
material-organizer
Organize only the materials the user has already provided or explicitly pointed to. The job is to make messy inputs easier to scan, reuse, archive, or continue from later while preserving source traceability.
swiftui-dev
Use this skill for SwiftUI development, architecture, structure, performance, and Apple native app profiling. It combines.
package-installer
Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.