oss-learn-stack

oss-learn-stack is a skill for Claude Code, Codex from chiruu12/OSS-Skills. It costs 79 tokens per session (2,231 once invoked), scanned A, original, MIT.

A hands-on guide to unfamiliar programming languages, frameworks, testing tools, build systems, and architecture patterns by studying how a specific repository uses them.

In plain words
What is it for?
Use it to identify the repository's technology stack, explain its patterns in context, and find relevant examples before contributing code.
Why use it?
It avoids relying only on generic documentation, which may not match the project's actual conventions or examples.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Install

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.

agentmods
npx agentmods add skills/chiruu12/oss-skills/oss-learn-stack
Any agent
npx skills add chiruu12/OSS-Skills --skill oss-learn-stack
Clone the repo
git clone --depth 1 https://github.com/chiruu12/OSS-Skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for oss-learn-stack

README.md
[![agentmods](https://agentmods.dev/badge/skills/chiruu12/oss-skills/oss-learn-stack.svg)](https://agentmods.dev/skills/chiruu12/oss-skills/oss-learn-stack)
Your own site
<a href="https://agentmods.dev/skills/chiruu12/oss-skills/oss-learn-stack"><img src="https://agentmods.dev/badge/skills/chiruu12/oss-skills/oss-learn-stack.svg" alt="Measured on agentmods" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,231 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00079 $0.02231
Opus 5 $0.00039 $0.01115
Sonnet 5 $0.00016 $0.00446
Haiku 4.5 $0.00008 $0.00223

Measured 6d ago against content hash 280e2d9ae8ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

oss-learn-stack 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 6d 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.

skills/oss-learn-stack/SKILL.md · 213 lines

How it starts

The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Learn Stack

Don't learn a framework from docs alone. learn it from how THIS repo uses it. This skill finds the patterns, explains the concepts, and points to real examples in the codebase you're about to contribute to.

Purpose

oss-prep-to-contribute does a knowledge check for one issue. This skill is broader: when a repo uses tech you don't know (unfamiliar language, framework, testing tool, build system, architecture pattern), this skill teaches those concepts using the repo itself as the textbook. Faster than reading generic docs because every example is from the actual codebase you'll contribute to.

Prerequisites

  • A repo cloned locally
  • At least a basic understanding of the project (from oss-explore-repo or your own exploration)
  • An honest assessment of what you don't know

Process

1. Identify the stack

Inventory the technologies used:

# Dependencies
cat package.json 2>/dev/null | jq '.dependencies, .devDependencies' 2>/dev/null
(cat requirements.txt 2>/dev/null || cat pyproject.toml 2>/dev/null) | head -40
cat go.mod 2>/dev/null | head -20
cat Cargo.toml 2>/dev/null | head -30

# Build and CI tools
ls .github/workflows/ 2>/dev/null
cat Makefile 2>/dev/null | head -20

# Testing
ls test/ tests/ __tests__/ spec/ 2>/dev/null
grep -l "jest\|pytest\|mocha\|vitest\|cargo test\|go test" * .* 2>/dev/null

# Linting and formatting
cat .eslintrc* .prettierrc* pyproject.toml tox.ini setup.cfg 2>/dev/null | head -30

Present the full stack categorized:

## Stack: {repo}

| Category | Technology |
|----------|-----------|
| Language | {e.g., TypeScript 5.x} |
| Framework | {e.g., Express.js} |
| Testing | {e.g., Vitest + Testing Library} |
| Build | {e.g., Vite} |
| CI | {e.g., GitHub Actions} |
| Linting | {e.g., ESLint + Prettier} |
| Database | {e.g., PostgreSQL via Prisma} |
| Other | {anything else notable} |

2. Find the user's gaps

Ask targeted questions:

"Here's the stack this repo uses. For each technology, tell me your comfort level:

  • Comfortable: used it in a project
  • Familiar: read about it, haven't used it
  • Unknown: never used it or only vaguely know what it is

Be honest. I'll focus teaching on the gaps. No judgment."

Read the full file on GitHub · 213 lines

Changes

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.

  1. 6d ago First seen · 213 lines · 79 tokens per session scan A 280e2d9ae8ce

Subscribe to this mod's changes

oss-learn-stack is a skill published in the GitHub repository chiruu12/OSS-Skills (62 stars, last pushed 12d ago), licensed MIT. It adds 79 tokens to every session and 2,231 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

iterate-pr

Iterate on a PR until CI passes. Optionally merge or merge and publish a release of the repo. Automates the feedback-fix-push-wait cycle.

meshery/meshery · 37 tokens

database-schema-designer

Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable data models.

meshery/meshery · 49 tokens

gen-relationship

Create and refine schema-backed Meshery relationship definitions (models//relationships/.json). Use for "add a relationship", "fix this relationship JSON", classifying kind/type/subType, or reviewing selectors and mutatorRef/mutatedRef patches between model components.

meshery/meshery · 57 tokens

agent-md-refactor

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

meshery/meshery · 40 tokens

command-creator

This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.

meshery/meshery · 66 tokens

cut-release

Cut (publish) a release of meshery/meshery by publishing the current Release Drafter draft. Use this whenever the user asks to "cut a release", "publish the release", "ship a release", "release meshery", "do a release", "release the latest merge", or wants recently merged PRs to go out to users. Handles waiting for…

meshery/meshery · 137 tokens