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 agentmods add rules/jasonchen0604/codebase-to-portfolio/generate-tech-profilegit clone --depth 1 https://github.com/jasonChen0604/codebase-to-portfolioWrote 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/rules/jasonchen0604/codebase-to-portfolio/generate-tech-profile)<a href="https://agentmods.dev/rules/jasonchen0604/codebase-to-portfolio/generate-tech-profile"><img src="https://agentmods.dev/badge/rules/jasonchen0604/codebase-to-portfolio/generate-tech-profile.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 | $0.00095 | $0.03319 |
| Opus 5 | $0.00048 | $0.01659 |
| Sonnet 5 | $0.00019 | $0.00664 |
| Haiku 4.5 | $0.00010 | $0.00332 |
Grade A, and why
generate-tech-profile 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 3d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Tech Profile Skill
Goal
Read all project docs (doc_filename) from projects that have the latest skill_version, extract structured frontmatter data (tags, category, status, description, etc.), then generate one Markdown file per configured language (languages in config, default ["en"]):
tech-profile-en.md— English version (ifenis inlanguages)tech-profile-<lang>.md— one file per additional configured language, e.g.tech-profile-zh-TW.md
All files share the same data and structure, but differ in language for all human-readable text. All are designed to be consumed by a personal website as the data source for skill tree / mind map rendering.
Step 0: Read config
Read profile.config.json from the current working directory. If missing, tell the user to copy examples/profile.config.example.json to profile.config.json and fill it in, then stop.
profile.name— used in the document title (e.g.# <name> — Personal Tech Profile)doc_filename(defaultCLAUDE.md)languages(default["en"])timezone(default+00:00) — used forgenerated_atprivacy_blocklist(default[]) — additional names to sanitize out ofdisplay_name, on top of the built-in rules belowcustom_domains(default{}) — extra tag → domain mappings merged into the built-in domain table in Step 5
Execution Steps
Step 1: Get the latest version
Run the /get-latest-version skill to obtain the current latest skill_version string (e.g. "2.0").
- If
noneis returned, abort and tell the user to run/batch-initfirst.
Step 2: Filter projects with latest version
Read projects-list.md and filter rows where:
- "Active" column is ✅
- Doc-file column is ✅
- "Version" column equals the latest version string from Step 1
Collect each matching project's Path column value, expanding ~ via $HOME.
Step 3: Read each project's doc frontmatter
For each filtered project path, read <path>/<doc_filename> and extract the YAML frontmatter block (between the --- delimiters).
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.
- 3d ago First seen · 268 lines · 95 tokens per session scan A b16e59f803c3
generate-tech-profile is a cursor rule published in the GitHub repository jasonChen0604/codebase-to-portfolio (2 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 3,319 once invoked, about $0.0005 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 cursor rules, from other repositories
the-loop
If .the-loop/config.yaml exists in this repository, the-loop is initialized here. Operating rules: plan → execute → self/critic-review → escalate. Read .the-loop/config.yaml and follow the the-loop skill before working any ticket. If the file does not exist, the-loop is not initialized — ignore this rule (or run…
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
lean
Answer densely. Cut filler, keep all technical signal.
orchestrator-main
Rules for the main orchestrator agent in multi-agent workflows.
react_hooks
React Hooks best practices for frontend package.