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 aida-core/aida-marketplace --skill project-contextgit clone --depth 1 https://github.com/aida-core/aida-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/aida-core/aida-marketplace/project-context)<a href="https://agentmods.dev/skills/aida-core/aida-marketplace/project-context"><img src="https://agentmods.dev/badge/skills/aida-core/aida-marketplace/project-context/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aida-core/aida-marketplace/project-context"><img src="https://agentmods.dev/badge/skills/aida-core/aida-marketplace/project-context.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.00572 |
| Opus 5 | $0.00008 | $0.00286 |
| Sonnet 5 | $0.00003 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
project-context 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 9d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context: aida-marketplace
This skill provides factual information about aida-marketplace's structure, tooling, and conventions. All information here is either auto-detected or explicitly configured for this project.
Project Facts
Project Name: aida-marketplace
Project Type: Unknown
Primary Language(s): TypeScript
Version Control: git
-
.gitignore: ✓
-
Worktree workflow: No
-
Branching model: GitHub Flow (feature branches → main)
Project Structure
Source Code Organization
Source organization: Flat structure (no src/ directory)
Code organization pattern: Follow existing pattern
Documentation
Documentation: README.md only
README: README.md (1592 chars - Standard - README, API docs, inline comments)
Changelog: None (changes tracked in git commits)
License: LICENSE
Testing
Testing framework: Minimal - manual testing only
Tests: Not yet set up
Tools & Infrastructure
Build/Package Management: package.json (Node/npm)
Development Tools: Git, GitHub Actions
Docker
Docker: Not used
CI/CD
CI/CD: GitHub Actions
Issue Tracking
Issue Tracking System: GitHub Issues
MCP Integration: ✅ GitHub MCP (official)
Claude should:
- Reference issues using #issue-number format
- Include "Fixes #123" or "Closes #123" in commit messages
- Suggest issue labels and milestones
- Use GitHub MCP for issue management
Project Conventions
Standard conventions - follow typical open-source project conventions
API Documentation
Guidelines for Claude
When working in this project:
Code Structure:
-
Place new files following the "Follow existing pattern" organization pattern
-
Follow flat project structure
-
Create tests directory when adding first test
Documentation:
- README.md only
Testing:
- Follow Minimal - manual testing only approach
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.
- 9d ago First seen · 128 lines · 16 tokens per session scan A edfd94f752c1
project-context is a skill published in the GitHub repository aida-core/aida-marketplace (4 stars, last pushed 2mo ago), licensed MPL-2.0. It adds 16 tokens to every session and 572 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
Context Budget Tuning
A review guide for tuning how much repository context an automated code review receives and how files are ranked for inclusion. It checks these settings against the chosen model and repository size.
setup
Initialize Conductor with product.md, tech-stack.md, and workflow.md.
varlock
Secure environment variable management with Varlock. Use when handling secrets, API keys, credentials, or any sensitive configuration. Ensures secrets are never exposed in terminal, logs, or LLM context. Provides guidance around integrating varlock into a project, reading/editing .env.schema and other .env files…
mindos-zh
A local knowledge-base assistant for storing and finding decisions, meeting notes, procedures, troubleshooting lessons, and preferences across conversations and coding agents. It works only with the MindOS knowledge base.
mindos
MindOS: local knowledge assistant & shared KB. Keeps decisions, notes, SOPs, debugging lessons, research findings, preferences across sessions/agents. Core: save notes, search KB, organize files, run workflows, review, append CSV, hand off context, distill lessons. NOT for app source or paths outside KB. Triggers…
mindos
Operate a MindOS knowledge base: update notes, search, organize files, execute SOPs/workflows, retrospective, append CSV, cross-agent handoff, route unstructured input to the right files, distill experience, sync related docs. Use when the task targets files inside the user's MindOS KB (mindRoot). NOT for editing app…