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/joomcode/joompulse-skills/growing-leaf-category-trackernpx skills add joomcode/joompulse-skills --skill growing-leaf-category-trackergit clone --depth 1 https://github.com/joomcode/joompulse-skillsWrote 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/joomcode/joompulse-skills/growing-leaf-category-tracker)<a href="https://agentmods.dev/skills/joomcode/joompulse-skills/growing-leaf-category-tracker"><img src="https://agentmods.dev/badge/skills/joomcode/joompulse-skills/growing-leaf-category-tracker.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.00213 | $0.03028 |
| Opus 5 | $0.00106 | $0.01514 |
| Sonnet 5 | $0.00043 | $0.00606 |
| Haiku 4.5 | $0.00021 | $0.00303 |
Grade A, and why
growing-leaf-category-tracker 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growing Leaf Category Tracker
This skill takes one category on Mercado Livre (Brasil) or Shopee Brasil and surfaces the sub-categories inside it that are growing fastest — the niches with the strongest month-over-month growth in estimated revenue. It helps a seller who already knows a broad area decide which specific niche to move into next.
How deep it can go differs by marketplace. On Mercado Livre the answer is the deep leaf niches below the third level of the category tree. On Shopee, category analytics exist only down to the third level, so the ranking runs at the deepest level available — the third — and anything deeper is folded into its level-3 ancestor and cannot be separated. Say so in the output; never pass level-3 rows off as deep leaves.
This is a niche-discovery snapshot, not a tracker over time. For a single category's opportunity index and market size, use the category-opportunity-index skill. To compare a category's aggregate numbers against a user-supplied previous snapshot, use the category-monitor skill. To find specific new products inside a category, use the new-growing-products-in-category skill.
Prerequisites
- JoomPulse MCP access is configured for the current agent environment.
- The user provides a marketplace — Mercado Livre (Brasil) or Shopee Brasil — and names a parent category (free text is fine).
- The available JoomPulse tools can resolve a category on either marketplace, walk its sub-categories, and return each one's current monthly market stats (estimated revenue and sales, number of active sellers, number of products) and the month-over-month movement in estimated revenue.
If JoomPulse MCP access is unavailable, stop and explain that the skill requires JoomPulse MCP setup before it can find growing niches.
Scope
- Mercado Livre (Brasil) and Shopee Brasil, one at a time. Other marketplaces are out of scope.
- Depth differs by marketplace: deep leaf niches below the third level on Mercado Livre; the third level only on Shopee, where deeper niches are folded into their level-3 ancestor.
- Sales and revenue are JoomPulse estimates — not real transactions. Disclose this in every output. The estimates are built differently on each marketplace: on Mercado Livre from historical listing data, on Shopee from the marketplace's own rounded sold counters refined with review movement. Use the matching disclaimer.
- Read-only. The skill never writes or modifies anything.
- Language: detect the seller's language and respond in it. Default to pt-BR.
- Keep the workflow invisible. Surface the answer, not the steps. Never fill
gaps from general knowledge; show
—for any missing value.
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 · 250 lines · 213 tokens per session scan A 0c5bc36d32b3
growing-leaf-category-tracker is a skill published in the GitHub repository joomcode/joompulse-skills (50 stars, last pushed 14d ago), licensed MIT. It adds 213 tokens to every session and 3,028 once invoked, about $0.0011 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.
Other skills, from other repositories
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
shopify-functions
Shopify Functions allow developers to customize the backend logic that powers parts of Shopify. Available APIs: Discount, Cart and Checkout Validation, Cart Transform, Pickup Point Delivery Option Generator, Delivery Customization, Fulfillment Constraints, Local Pickup Delivery Option Generator, Order Routing Location…
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
amazon-price-tracker
Amazon price monitoring and competitive pricing intelligence. Real-time price tracking, Buy Box analysis, promotion detection, and dynamic pricing strategy optimization. Use when the user asks about price monitoring, competitor pricing, Buy Box tracking, or pricing strategy.
ecommerce-landing-page
Audit and optimize e-commerce landing pages for conversion. CTA placement, trust signals, page structure, copy optimization, and A/B testing strategy for product pages, collection pages, and campaign landing pages.