write-memo

write-memo is a skill for Claude Code, Codex from edinetdb/dexter-jp. It costs 100 tokens per session (2,782 once invoked), scanned A, original, MIT.

A structured HTML document that presents an analyst’s case for buying or shorting a company’s stock. It covers the trade’s direction, time frame, supporting data, scenarios, risks, and optional valuation work.

In plain words
What is it for?
Preparing long or short stock memos, gathering financial and market information, comparing bear, base, and bull outcomes, and producing a self-contained HTML file.
Why use it?
It gives a repeatable format for turning scattered research into a clear, testable investment argument, including the opposing case.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Good fit Preparing long or short stock memos, gathering financial and market information, comparing bear, base, and bull outcomes, and producing a self-contained HTML file.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/edinetdb/dexter-jp/write-memo
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 edinetdb/dexter-jp --skill write-memo
Clone the repo
git clone --depth 1 https://github.com/edinetdb/dexter-jp

Made for: Claude Code, Codex.

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.

agentmods badge for write-memo

README.md
[![agentmods](https://agentmods.dev/badge/skills/edinetdb/dexter-jp/write-memo.svg)](https://agentmods.dev/skills/edinetdb/dexter-jp/write-memo)
Your own site
<a href="https://agentmods.dev/skills/edinetdb/dexter-jp/write-memo"><img src="https://agentmods.dev/badge/skills/edinetdb/dexter-jp/write-memo.svg" alt="Measured on agentmods" height="20"></a>
Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,782 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium System Prompt Leakage · line 4
    Skill contains patterns that could indirectly extract system prompts through rephrasing, translation, summarization, or side-channel techniques.
    Fix: Guard against indirect extraction by refusing to summarize, translate, or rephrase system instructions. Add explicit anti-extraction clauses.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00100 $0.02782
Opus 5 $0.00050 $0.01391
Sonnet 5 $0.00020 $0.00556
Haiku 4.5 $0.00010 $0.00278

Measured 8d ago against content hash 63a2019371ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

write-memo 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 8d 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.

src/skills/write-memo/SKILL.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Write Investment Memo Skill

Produces a buyside-quality investment memo as a self-contained HTML file. The memo is opinionated and falsifiable — it leads with a variant view and steelmans the bear case. The output is the deliverable; the chat response is just a header summary plus the file path.

Workflow Checklist

Copy and track progress:

Investment Memo Progress:
- [ ] Step 1: Frame the trade (direction, horizon, variant view)
- [ ] Step 2: Gather data (financials, market, filings)
- [ ] Step 3: Build Bear / Base / Bull scenarios
- [ ] Step 4: Optional DCF anchor for base case
- [ ] Step 5: Draft memo content (fill all slots)
- [ ] Step 6: Self-critique pass
- [ ] Step 7: Render HTML to .dexter/memos/
- [ ] Step 8: Report header summary + file path

Step 1: Frame the Trade

Confirm or ask for the following before drafting:

  • Ticker (required)
  • Direction: long or short (required)
  • Horizon: 3mo / 6mo / 12mo / 2yr+ (default 12mo if not specified)
  • Conviction: high / medium / low (default medium)
  • Variant view: one sentence — what the analyst sees that consensus doesn't

If the user does not provide a variant view: do not ask repeatedly. Gather data in Step 2 first, then derive a candidate variant view from where your model meaningfully diverges from consensus (e.g., "our '27 EPS is $X vs consensus $Y because [driver]"). Present it as a draft and let the analyst accept, refine, or replace before you proceed to Step 5.

Step 2: Gather Data (Parallel)

Issue these tool calls in parallel:

2.1 Financials

Call get_financials:

  • "[TICKER] annual income statements last 5 years" — revenue, operating income, net income, EPS, margins
  • "[TICKER] annual cash flow statements last 5 years" — operating CF, capex, FCF
  • "[TICKER] latest balance sheet" — debt, cash, shares outstanding
  • "[TICKER] financial metrics snapshot" — P/E, EV, ROIC, FCF growth, debt/equity, margins
  • "[TICKER] segmented financials" — segment revenue, segment margins (if multi-segment)
  • "[TICKER] earnings history last 8 quarters" — beats/misses, surprises
  • "[TICKER] company facts" — sector, industry, market cap
  • "[TICKER] KPI guidance" and "[TICKER] KPI metrics" — management-provided KPIs and guidance

Read the full file on GitHub · 193 lines

Files

What ships with it

3 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.

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.

  1. 8d ago First seen · 193 lines · 100 tokens per session scan A 63a2019371ac

Subscribe to this mod's changes

write-memo is a skill published in the GitHub repository edinetdb/dexter-jp (304 stars, last pushed 3d ago), licensed MIT. It adds 100 tokens to every session and 2,782 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-30.