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 skills/jasonchen0604/codebase-to-portfolio/init-project-docnpx skills add jasonChen0604/codebase-to-portfolio --skill init-project-docgit 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/skills/jasonchen0604/codebase-to-portfolio/init-project-doc)<a href="https://agentmods.dev/skills/jasonchen0604/codebase-to-portfolio/init-project-doc"><img src="https://agentmods.dev/badge/skills/jasonchen0604/codebase-to-portfolio/init-project-doc.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.00079 | $0.01591 |
| Opus 5 | $0.00039 | $0.00796 |
| Sonnet 5 | $0.00016 | $0.00318 |
| Haiku 4.5 | $0.00008 | $0.00159 |
Grade A, and why
init-project-doc 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 4d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init Project Doc Skill
Role
You are a senior software architect and personal-brand consultant. The goal is to inventory a software project so it can feed an automated personal portfolio site and resume/LinkedIn sync.
Trigger
The user provides a project's directory tree and/or core source snippets, and asks for a project doc to be generated.
Execution Steps
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.
doc_filename(defaultCLAUDE.md) — the output filenamelanguages(default["en"]) — output language(s) for descriptive texttimezone(default+00:00) — used for thegenerated_attimestamp
Step 1: Read reference files
Read the following files, located in this skill's directory:
config.json→allowed_categoriesandallowed_statusesliststemplate.md→ output format (with YAML frontmatter) and all{{VARIABLE}}fields
Step 2: Analyze project code
From the user-provided tree structure and source code, identify:
- Core language & framework (e.g. TypeScript + Next.js, Python + FastAPI)
- Database / storage layer (e.g. PostgreSQL, Redis, SQLite)
- Build tools / package manager (e.g. pnpm, Poetry, Gradle)
- Deployment / cloud services (e.g. Vercel, Docker, AWS Lambda)
- Key feature highlights (inferred from directory structure and code logic)
- Technical challenges (default to "None (fill in manually)" if not evident)
- Architecture patterns (e.g. MVC, Repository Pattern, Event-Driven)
- State management (e.g. Zustand, Redux, Context API, none)
- Auth / authorization mechanism (e.g. NextAuth, JWT, OAuth, none)
Step 3: Apply constraints
category: must exactly match one item fromallowed_categories— do not invent new onesstatus: must exactly match one item fromallowed_statuses— do not invent new onesfeatured: alwaysfalsegithub_repo_name: inferred from the project directory name (empty string if unclear)cover_image: always empty string""
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 111 lines · 79 tokens per session scan A 8756d0859625
init-project-doc is a skill published in the GitHub repository jasonChen0604/codebase-to-portfolio (2 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 1,591 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-31.
Other skills, from other repositories
a11y-analyzer
Accessibility analysis from session data — keyboard-only navigation patterns, focus order issues, screen reader compatibility, and accessibility regressions. Use when auditing a11y compliance, investigating accessibility bugs, or validating inclusive design.
campaign-tracker
Track marketing campaign performance — UTM-tagged traffic, landing page conversion, campaign cohort behavior, and ROI signals. Use when analyzing campaign performance, measuring landing page effectiveness, or comparing marketing channels.
changelog-detective
Detect what changed in the product by comparing before and after a deploy or date — find new behaviors, new errors, changed user flows, and unexpected side effects that weren't in the release notes. Use after a deploy or when the user suspects something changed but doesn't know what.
form-analyzer
Form field-level analysis — abandonment by field, validation errors, time-to-complete, and which fields cause users to leave. Use when investigating form performance, signup drop-off, or checkout form friction.
funnel-doctor
Conversion funnel analysis — find where users drop off, quantify the loss, and diagnose why. Use when asking about conversion rates, funnel abandonment, checkout completion, signup flow performance, or "where are we losing users.".
heatmap-generator
Generate click and interaction heatmaps from session data — visualize where users click, tap, and hover on any page. Use when asking "what do users click on most", "are users clicking non-clickable elements", or "where should we place the CTA".