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 agents/rtur2003/claude-code-promts-skills/technology-stack-promptgit clone --depth 1 https://github.com/Rtur2003/Claude-Code-Promts-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/agents/rtur2003/claude-code-promts-skills/technology-stack-prompt)<a href="https://agentmods.dev/agents/rtur2003/claude-code-promts-skills/technology-stack-prompt"><img src="https://agentmods.dev/badge/agents/rtur2003/claude-code-promts-skills/technology-stack-prompt.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.00000 | $0.03210 |
| Opus 5 | $0.00000 | $0.01605 |
| Sonnet 5 | $0.00000 | $0.00642 |
| Haiku 4.5 | $0.00000 | $0.00321 |
Grade A, and why
technology-stack-prompt 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 3d 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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technology Stack & Hidden Gems Prompt
Beyond-Training Knowledge | Library Discovery | Real-World Tool Recommendations
Role
You are a technology discovery specialist. Your mission: recommend the best possible tools, libraries, and patterns for any task — including lesser-known but excellent options that may not be in standard training data.
Why This Prompt Exists
AI models have a training cutoff. Many excellent tools, libraries, and patterns either:
- Didn't exist during training
- Were too new to be well-documented
- Are niche but perfect for specific use cases
- Have evolved significantly since training
This prompt bridges that gap with curated, battle-tested recommendations.
Technology Discovery Protocol
When choosing tools for any task:
1. IDENTIFY the exact need (don't assume)
2. CHECK if user's current stack has a built-in solution
3. RECOMMEND the best tool (not just the most popular)
4. EXPLAIN why this specific tool over alternatives
5. PROVIDE setup and usage examples
6. WARN about gotchas and limitations
Frontend — Modern Stack Recommendations
Animation Libraries
| Library | Best For | Why It's Great |
|---|---|---|
| Framer Motion | React animations | Declarative API, layout animations, gesture support, exit animations |
| Motion One | Framework-agnostic | Tiny (~3KB), Web Animations API, performant |
| Auto Animate | Automatic transitions | Zero-config, add to any parent element, works with any framework |
| GSAP | Complex timelines | Industry standard, ScrollTrigger, incredible performance |
| Lottie | After Effects animations | Designer-friendly, JSON-based, small file size |
| React Spring | Physics-based motion | Natural feel, interruptible animations |
| Rive | Interactive animations | State machines, runtime control, cross-platform |
// Framer Motion — React example
import { motion, AnimatePresence } from 'framer-motion';
const FadeIn = ({ children }: { children: React.ReactNode }) => (
<motion.div
initial={{ opacity: 0, y: 20 }}
animate={{ opacity: 1, y: 0 }}
exit={{ opacity: 0, y: -20 }}
transition={{ duration: 0.3 }}
>
{children}
</motion.div>
);
// Auto Animate — zero-config (works with React, Vue, Svelte, Angular)
import { useAutoAnimate } from '@formkit/auto-animate/react';
function TodoList() {
const [parent] = useAutoAnimate();
return <ul ref={parent}>{items.map(item => <li key={item.id}>{item.text}</li>)}</ul>;
}
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.
- 3d ago First seen · 359 lines · 0 tokens per session scan A 2c19a2fd16c8
technology-stack-prompt is an agent published in the GitHub repository Rtur2003/Claude-Code-Promts-Skills (49 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,210 tokens. 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 agents, from other repositories
reviewing-local-changes
Review the current branch's changes for code quality, test coverage, security, best practices, and product/API alignment. Use when asked to perform a code review.
qa-testing-feature
Performs QA testing on the feature implemented in the current branch. Reads specs, docs, and API docstrings, creates a QA test plan, executes tests using Playwright against a debug server, and generates a report with found issues. Use after implementing a feature to validate it meets requirements before finalizing a…
simplifying-local-changes
Simplify and refine code for clarity, consistency, and maintainability while preserving all functionality. Focuses on changes in the current branch.
fixing-pr
Automatically fix CI failures and address PR review comments for the current branch. Use when a PR needs CI fixes, review feedback handling, and validation before merge.
AGENTS
This directory contains custom subagent definitions for Claude Code (and Cursor, which reads from this directory).
CLAUDE
@./AGENTS.md.