A teaching module for command-line work, where developers control a computer by typing commands. It covers navigation, file operations, npm—the package manager for JavaScript projects—and basic shell and Git usage.

Learning commands such as `cd`, `ls`, `pwd`, `mkdir`, `cp`, `mv`, and `rm`, plus basic npm, shell, and Git workflows.

It makes terminal tasks easier to understand for people who are new to text-based computer tools. It also highlights that deleting with `rm` is permanent.

terminal — Skill for Claude Code by DojoCodingLabs/code-sensei

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.

Any agent

npx skills add DojoCodingLabs/code-sensei --skill terminal

Clone the repo

git clone --depth 1 https://github.com/DojoCodingLabs/code-sensei

Made for: Claude Code.

Or install code-sensei, the plugin that ships this one along with the rest of its 10 skills, 10 commands, 1 agent, 3 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dojocodinglabs/code-sensei/terminal/github.svg)](https://agentmods.dev/skills/dojocodinglabs/code-sensei/terminal)

Your own site

<a href="https://agentmods.dev/skills/dojocodinglabs/code-sensei/terminal"><img src="https://agentmods.dev/badge/skills/dojocodinglabs/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/dojocodinglabs/code-sensei/terminal"><img src="https://agentmods.dev/badge/skills/dojocodinglabs/code-sensei/terminal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 693 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

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

Measured 1mo ago against content hash 0840f41b7519, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

terminal — 100% identical, 0 lines differ

skills/terminal/SKILL.md · 54 lines

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 folder
ls — "List" — see what's in the current folder
pwd — "Print Working Directory" — "where am I right now?"
Analogy: You're in a building. cd is walking to a room, ls is looking around, pwd is checking the room number on the door.

File Operations

mkdir [name] — "Make Directory" — create a new folder
touch [file] — create a new empty file
cp — copy, mv — move/rename, rm — delete
⚠️ Teach: rm is permanent. There's no trash can.

npm (Node Package Manager)

Analogy: An app store for code. Other developers built tools and shared them. npm install downloads those tools into your project.
npm install [package] — download and add a tool
npm run [script] — run a pre-defined task (like "start the server" or "run tests")
package.json — the shopping list of all tools your project uses
node_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 description
git 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.
.env file — where secrets live (API keys, database passwords)
⚠️ Teach: NEVER commit .env files to git. That's like posting your passwords publicly.

Read the full file on GitHub · 54 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.

1mo ago First seen · 54 lines · 31 tokens per session scan A 0840f41b7519

Subscribe to this mod's changes

terminal is a skill published in the GitHub repository DojoCodingLabs/code-sensei (14 stars, last pushed 22d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Git and workflow Learning and teaching ai-mentor anthropic beginner claude-code-commands claude-code-hooks

cloudflare-workers-ci-cd

Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.

secondsky/claude-skills · 50 tokens

claude-code-bash-patterns

Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.

secondsky/claude-skills · 52 tokens

pr-queue

Run a pull-request (or issue) queue for an area of alchemy — search GitHub for open PRs/issues matching a criteria (e.g. "cloudflare", "docker", "aws/rds", an author, a label), shortlist the top 10 ordered by ease of fixing, then work through them one at a time: check out, merge main, resolve conflicts, audit tests…

systemfsoftware/comment-checker · 161 tokens

terminal