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 wewpellex21/code-sensei --skill terminalgit clone --depth 1 https://github.com/wewpellex21/code-senseiWrote 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/wewpellex21/code-sensei/terminal)<a href="https://agentmods.dev/skills/wewpellex21/code-sensei/terminal"><img src="https://agentmods.dev/badge/skills/wewpellex21/code-sensei/terminal/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/wewpellex21/code-sensei/terminal"><img src="https://agentmods.dev/badge/skills/wewpellex21/code-sensei/terminal.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.00031 | $0.00693 |
| Opus 5.5 | $0.00012 | $0.00277 |
| Sonnet 5.5 | $0.00006 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
terminal 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 1mo 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.
This is a copy
100% identical to terminal — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terminal & Command Line — CodeSensei Teaching Module
The Terminal
- Analogy: The terminal is like texting your computer. Instead of clicking buttons, you type instructions and it responds. It's not scarier than that.
- Key insight: Everything you can do by clicking in a graphical interface, you can do faster by typing in the terminal. Developers prefer typing because it's faster and scriptable.
Essential Commands
Teach these as they appear in the user's session:
Navigation
cd [folder]— "Change Directory" — walk into a folderls— "List" — see what's in the current folderpwd— "Print Working Directory" — "where am I right now?"- Analogy: You're in a building.
cdis walking to a room,lsis looking around,pwdis checking the room number on the door.
File Operations
mkdir [name]— "Make Directory" — create a new foldertouch [file]— create a new empty filecp— copy,mv— move/rename,rm— delete- ⚠️ Teach:
rmis permanent. There's no trash can.
npm (Node Package Manager)
- Analogy: An app store for code. Other developers built tools and shared them.
npm installdownloads those tools into your project. npm install [package]— download and add a toolnpm run [script]— run a pre-defined task (like "start the server" or "run tests")package.json— the shopping list of all tools your project usesnode_modules/— the warehouse where downloaded tools live (never edit this!)
git (Version Control)
- Analogy: A time machine for your code. Every "commit" is a save point you can go back to.
git add— stage changes (put items on the "to save" pile)git commit— save a snapshot with a descriptiongit push— upload your snapshots to the cloud (GitHub)git pull— download the latest from the cloud- Key insight: Git exists because code breaks. It lets you undo mistakes by going back to when things worked.
Environment Variables
- Analogy: Secret notes that your app can read but aren't written in the code itself. Like a password you whisper instead of writing on a whiteboard.
.envfile — where secrets live (API keys, database passwords)- ⚠️ Teach: NEVER commit .env files to git. That's like posting your passwords publicly.
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.
- 1mo ago First seen · 54 lines · 31 tokens per session scan A 0840f41b7519
terminal is a skill published in the GitHub repository wewpellex21/code-sensei (3 stars, last pushed 12d ago), licensed MIT. It adds 31 tokens to every session and 693 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to terminal, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
aws-cdk-development
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python. Use when creating CDK stacks, defining CDK constructs, implementing infrastructure as code, or when the user mentions CDK, CloudFormation, IaC, cdk synth, cdk deploy, or wants to define AWS infrastructure programmatically.…
aws-agentic-ai
AWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale. Use when working with any AgentCore service including Gateway, Runtime, Memory, Identity, Code Interpreter, Browser, Observability, Agent Registry, or Evaluations. Covers agent deployment, MCP tool integration, credential…
harnessay
Use when analyzing Claude Code or Codex context usage, repeated workflows, skill candidates, or skill regression tests. Triggers include harnessay, context report, and where did my tokens go.
canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
senior-frontend
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.