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 glincker/claude-code-marketplace --skill hello-worldgit clone --depth 1 https://github.com/glincker/claude-code-marketplaceWrote 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/glincker/claude-code-marketplace/hello-world)<a href="https://agentmods.dev/skills/glincker/claude-code-marketplace/hello-world"><img src="https://agentmods.dev/badge/skills/glincker/claude-code-marketplace/hello-world.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.00012 | $0.00753 |
| Opus 5 | $0.00006 | $0.00377 |
| Sonnet 5 | $0.00002 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
hello-world 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hello World Skill
This is a simple example skill that demonstrates the basic structure and format of a Claude Code skill. It's perfect for learning how skills work!
What This Skill Does
When activated, this skill helps Claude:
- Greet users in a friendly, informative way
- Explain what skills are and how they work
- Provide guidance on next steps
This skill doesn't require any tools, making it the simplest possible example.
Instructions
When this skill is activated:
- Greet the user warmly
- Explain that this is a demonstration of Claude Code skills
- Briefly describe what skills are and how they extend Claude's capabilities
- Suggest exploring other skills in the marketplace
- Offer to help the user create their own skill
Keep the tone friendly, encouraging, and educational.
Examples
Example 1: Basic Activation
User Request: "Use the hello-world skill"
Expected Response: "Hello! I'm using the Hello World skill, which is a simple demonstration of how Claude Code skills work.
Skills are modular capabilities that extend what I can do. Each skill is just a folder with a SKILL.md file that contains instructions for me to follow. This particular skill doesn't need any tools, so it's a great starting point for learning!
The GLINCKER Marketplace has many more skills you can explore:
- Development tools
- Productivity enhancers
- Creative assistants
- And much more!
Would you like to explore other skills, or shall I help you create your own?"
Tool Requirements
This skill requires no tools - it's purely instructional, making it the perfect beginner example.
Limitations
This is an educational skill with no practical functionality:
- It doesn't modify files or execute commands
- It's designed purely for demonstration purposes
- For real work, explore the other skills in the marketplace
Best Practices
This skill demonstrates several best practices:
- Clear frontmatter: All required fields are present
- Minimal permissions: No tools requested (since none are needed)
- Good documentation: Clear explanation of purpose and usage
- Examples provided: Shows expected behavior
- Simple structure: Easy to understand and learn from
What ships with it
1 file 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 · 113 lines · 12 tokens per session scan A af856ef5a805
hello-world is a skill published in the GitHub repository glincker/claude-code-marketplace (36 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 753 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
implementing-secret-scanning-with-gitleaks
This skill covers implementing Gitleaks for detecting and preventing hardcoded secrets in git repositories. It addresses configuring pre-commit hooks, CI/CD pipeline integration, custom rule authoring for organization-specific secrets, baseline management for existing repositories, and remediation workflows for…
integrating-sast-into-github-actions-pipeline
This skill covers integrating Static Application Security Testing (SAST) tools—CodeQL and Semgrep—into GitHub Actions CI/CD pipelines. It addresses configuring automated code scanning on pull requests and pushes, tuning rules to reduce false positives, uploading SARIF results to GitHub Advanced Security, and…
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
implementing-infrastructure-as-code-security-scanning
This skill covers implementing automated security scanning for Infrastructure as Code (IaC) templates using tools like Checkov, tfsec, and KICS. It addresses detecting misconfigurations in Terraform, CloudFormation, Kubernetes manifests, and Helm charts before deployment, establishing policy-based governance, and…
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
performing-sca-dependency-scanning-with-snyk
This skill covers implementing Software Composition Analysis (SCA) using Snyk to detect vulnerable open-source dependencies in CI/CD pipelines. It addresses scanning package manifests and lockfiles, automated fix pull request generation, license compliance checking, continuous monitoring of deployed applications, and…