Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Aznatkoiny/zAI-Skills/plugin install real-estate-investmentWrote 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/commands/aznatkoiny/zai-skills/portfolio)<a href="https://agentmods.dev/commands/aznatkoiny/zai-skills/portfolio"><img src="https://agentmods.dev/badge/commands/aznatkoiny/zai-skills/portfolio.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.1 | $0.00019 | $0.00679 |
| Opus 5 | $0.00010 | $0.00340 |
| Sonnet 5 | $0.00004 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
portfolio 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portfolio Tracker & Review
Requested action and details (may be empty): $ARGUMENTS
Instructions
When this command is invoked, maintain the user's persistent portfolio file and review it:
1. Locate or Create portfolio.json
Look for portfolio.json in the current working directory (Glob/Read).
- Exists: Read it and confirm the property count and
as_ofdate with the user - Missing: create it from the plugin template — Read
${CLAUDE_PLUGIN_ROOT}/templates/portfolio-template.json, keep its_schemablock, replace the example entries with the user's actual properties, and setas_ofto today
2. Apply the Requested Change
Interpret $ARGUMENTS (or ask):
- add: collect the schema fields for the new property via AskUserQuestion — required:
property,basis,debt,rate+maturity(if debt > 0),rent,noi,value; recommended:type,acquired,accumulated_depreciation,value_source,notes - update: locate the entry by address (fuzzy match is fine, confirm the match), update the named fields, refresh
as_of - remove: delete the entry after confirmation (suggest
/exit-analysisfirst if they are selling rather than just cleaning up) - review (or no action given): skip straight to step 4
Validate before writing: numbers are plain numbers, rates are decimals (0.065 not 6.5), dates are YYYY-MM-DD, debt <= value sanity check (warn, don't block). Write the updated file with Write, preserving the _schema block and any fields you did not touch.
3. Confirm the Write
Show a one-line-per-property summary table (address, value, debt, NOI, rate, maturity) so the user can spot typos before analysis runs.
4. Run the Portfolio Review
Invoke the portfolio-reviewer agent, telling it to read portfolio.json in the working directory as its data source. It aggregates portfolio metrics (LTV, weighted cap rate, portfolio DSCR, CoC), flags concentration and refinance risks, ranks property performance, and recommends optimization moves.
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 · 53 lines · 19 tokens per session scan A 84ad1d020791
portfolio is a command published in the GitHub repository Aznatkoiny/zAI-Skills (9 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 679 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, and GCP.
strip
This is the task-based stripper, not the always-on prior: a deliberate cleanup pass you asked for. Apply the fp-minify doctrine to the target and remove or compress comments that don't earn their place.
setup
A command that creates a Korean-language CLAUDE.md project guide from a template. CLAUDE.md is a file containing instructions and project context for the Claude coding assistant.
dock-chat
Dock the full conversation to Telegram — drive Claude from your phone.
conjure-agent
Creates or updates a Claude Code agent definition (/.claude/agents/ .md or project-local).
conjure-mcp
Create a Claude Code MCP (Model Context Protocol) server. Provide a description of what external system or data source you want Claude to connect to.