trend-analysis

trend-analysis is a skill for Claude Code from awslabs/agentcore-samples. It costs 21 tokens per session (385 once invoked), scanned A, original, Apache-2.0.

A stock-market analysis workflow that examines price, trading volume, sector performance, and recent news to classify whether a stock is moving up, down, or sideways.

In plain words
What is it for?
Use it to review stock momentum, estimate nearby support and resistance levels, and produce a structured trend report with a confidence rating.
Why use it?
It turns several market signals into one consistent view, reducing the need to gather and compare them manually.

Skill for Claude Code ✓ vendor

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to review stock momentum, estimate nearby support and resistance levels, and produce a structured trend report with a confidence rating.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/awslabs/agentcore-samples/trend-analysis
About the project

Amazon Bedrock AgentCore Samples is a collection of examples and tutorials for deploying and operating AI agents with Amazon Bedrock AgentCore. Developers use it to integrate agent applications built with different frameworks and language models while learning AgentCore features. The catalogue add-ons provide agent-oriented guidance for working with these samples and services.

awslabs/agentcore-samples · 3,457 stars · on GitHub · aws.amazon.com

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 awslabs/agentcore-samples --skill trend-analysis
Clone the repo
git clone --depth 1 https://github.com/awslabs/agentcore-samples

Made for: Claude Code.

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 trend-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/awslabs/agentcore-samples/trend-analysis/github.svg)](https://agentmods.dev/skills/awslabs/agentcore-samples/trend-analysis)
Your own site
<a href="https://agentmods.dev/skills/awslabs/agentcore-samples/trend-analysis"><img src="https://agentmods.dev/badge/skills/awslabs/agentcore-samples/trend-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for trend-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/awslabs/agentcore-samples/trend-analysis"><img src="https://agentmods.dev/badge/skills/awslabs/agentcore-samples/trend-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 385 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 pass 7 Sept 2026
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.00021 $0.00385
Opus 5.5 $0.00008 $0.00154
Sonnet 5.5 $0.00004 $0.00077
Haiku 4.5 $0.00002 $0.00038

Measured 1mo ago against content hash 8184b68a91e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

trend-analysis 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 1mo 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.

02-use-cases/01-conversational-agents/market-trends-agent/skills/trend-analysis/SKILL.md · 40 lines

What it actually says

Trend Analysis Skill

Use this skill when a user asks about price trends, momentum, technical analysis, or whether a stock is trending up or down.

Required workflow

  1. Retrieve current stock data using get_stock_data for each symbol in the request.
  2. Retrieve sector data for the stock's sector using get_sector_data.
  3. Search for recent news affecting the stock using search_news with the stock's sector.
  4. Evaluate momentum: classify the trend as Uptrend, Downtrend, or Sideways based on:
    • Daily price change direction and magnitude
    • Sector trend (outperforming / underperforming / neutral)
    • News sentiment (positive / negative / mixed)
  5. Identify key support level: approximate as price × 0.95 (−5% from current).
  6. Identify key resistance level: approximate as price × 1.05 (+5% from current).
  7. Assign a confidence score (Low / Medium / High) based on alignment across price, sector, and news signals.
  8. Output a structured Trend Analysis Report with: symbol, current price, trend direction, momentum signal, key levels, and confidence.

Output Format

Trend Analysis: {SYMBOL}
  Price       : ${price}  ({change_pct:+.2f}% today)
  Trend       : {Uptrend | Downtrend | Sideways}
  Momentum    : {signal description}
  Support     : ${support}
  Resistance  : ${resistance}
  Confidence  : {Low | Medium | High}
  Summary     : {1-2 sentence rationale}
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. 1mo ago First seen · 40 lines · 21 tokens per session scan A 8184b68a91e0

Subscribe to this mod's changes

trend-analysis is a skill published in the GitHub repository awslabs/agentcore-samples (3,457 stars, last pushed 3d ago), licensed Apache-2.0. It adds 21 tokens to every session and 385 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

travel-expense-audit

A travel-expense review workflow that checks reimbursement claims against policy handbooks and rate tables. It covers items such as hotel, transport, and daily meal allowances.

vixues/LeAgent · 51 tokens

risk-scoring

Score how concentrated and risky a portfolio is on a 0-100 scale from its position weights. Use when the user asks how risky their portfolio is, whether it is too concentrated, or for a diversification check.

microsoft/agent-framework · 47 tokens

kirocrew-app-dev

Build, package, and publish Kiro Crew external apps. Covers app.json manifests, UI components, crons, skills, lifecycle hooks, development mode, registry publishing, and common pitfalls.

kirodotdev/KiroCrew · 44 tokens

goal-conductor

Own a goal too large for one session ('clear the flaky-test backlog', 'push N PRs green') end to end via the work ledger — decompose into items, one session per item, read worker status as data, verify claims with the acceptance evaluator, decide each round until done. Use when handed such a goal.

kirodotdev/KiroCrew · 70 tokens

security-conductor

Operating procedure for the kirocrew-security-conductor agent. Use when a security conductor session is seeded, inspected or debugged. Run vulnerability discovery on one target as a supervised fleet — one auditor per attack surface, an independent verifier per finding, two human gates.

kirodotdev/KiroCrew · 57 tokens

computer-use

Read and drive native desktop apps through the accessibility layer — list apps, snapshot a window as a numbered element tree, then click/type/scroll/drag by element index or screen coordinates. Use for a desktop app, not a web page. macOS + Windows; off unless enabled in Settings.

kirodotdev/KiroCrew · 62 tokens