gsp-project-research

gsp-project-research is a skill for Claude Code from jubscodes/get-shit-pretty. It costs 0 tokens per session (1,616 once invoked), scanned A, original, MIT.

A research workflow for understanding a product, its user flows, and the technical problems involved. It stores six research sections in the project workspace.

In plain words
What is it for?
Use it to investigate how a product should work, study similar patterns, and identify implementation challenges before design or coding.
Why use it?
It gives a project a structured place for research instead of leaving findings scattered across notes or guesses.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is | UX Patterns | [ux-patterns.md](../research/ux-patterns.md) |.

Good fit Use it to investigate how a product should work, study similar patterns, and identify implementation challenges before design or coding.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/jubscodes/get-shit-pretty
agentmods
npx agentmods add skills/jubscodes/get-shit-pretty/gsp-project-research

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 gsp-project-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-project-research/github.svg)](https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-project-research)
Your own site
<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-project-research"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-project-research/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 gsp-project-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-project-research"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-project-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,616 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.
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.00000 $0.01616
Opus 5 $0.00000 $0.00808
Sonnet 5 $0.00000 $0.00323
Haiku 4.5 $0.00000 $0.00162

Measured 10d ago against content hash 5e5fbd4eb279, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

gsp-project-research 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 10d 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.

gsp/skills/gsp-project-research/SKILL.md · 156 lines

How it starts

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

This is NOT brand-level discovery (that's /gsp-brand-research). This is project-level research — focused on the product type, user flows, and implementation challenges.

Works with the dual-diamond architecture: reads brand context from .design/branding/{brand}/ via brand.ref, reads/writes project assets in .design/projects/{project}/.

Input: Brief scope + brand system + project BRIEF.md Output: {project}/research/ (6 research chunks + INDEX.md) Agent: gsp-project-researcher Output mode: Honor ${CLAUDE_SKILL_DIR}/../../policies/output-modes.md per preferences.project_size (default compact). Chunk file counts and consolidation rules live in the policy.

<execution_context> @${CLAUDE_SKILL_DIR}/../../templates/phases/research.md </execution_context>

If .design/projects/ does not exist: output "No GSP project found. Run /gsp-start to begin." and stop.

Resolve project from .design/projects/ (one → use it, multiple → ask). Set PROJECT_PATH.

Read {PROJECT_PATH}/brand.ref → set BRAND_PATH.

Step 1: Load context

Brief (chunk-first)

Read {PROJECT_PATH}/brief/INDEX.md. If it exists, load scope.md and target-adaptations.md.

If brief doesn't exist, tell the user to run /gsp-project-brief first.

Brand system (selective)

Read {BRAND_PATH}/patterns/INDEX.md. If it exists, load foundation chunks (to understand the design system constraints).

Brand discovery (selective)

Read {BRAND_PATH}/discover/INDEX.md. If it exists, load competitive-audit.md and trend-analysis.md (to avoid duplicating brand-level research).

Read the full file on GitHub · 156 lines

Files

What ships with it

1 file 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. 10d ago First seen · 156 lines · 0 tokens per session scan A 5e5fbd4eb279

Subscribe to this mod's changes

gsp-project-research is a skill published in the GitHub repository jubscodes/get-shit-pretty (54 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,616 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.

Related

Other skills, from other repositories

opencli-usage

Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".

jackwener/OpenCLI · 74 tokens

opencli-sitemap-author

Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.

jackwener/OpenCLI · 67 tokens

opencli-browser-sitemap

Use when driving a website with opencli browser and sitemap context is available, requested, or needed to avoid blind navigation. Guides agents to consume site sitemap files lazily, choose adapter/browser fallback paths, resume from state signatures, and mark stale sitemap entries without trusting them over live…

jackwener/OpenCLI · 64 tokens

gpt-vis

A chart-generation tool that recommends visual formats for data and produces either chart settings or runnable code. It uses GPT-Vis, a library for rendering data visualisations.

antvis/chart-visualization-skills · 63 tokens

infographic-creator

Create beautiful infographics based on given text content. Use when users request to create infographics.

antvis/chart-visualization-skills · 24 tokens

antv-x6-editor

A skill for creating and troubleshooting interactive diagrams with AntV X6, a JavaScript engine for editors made of connected nodes and lines. It supports diagram types such as flowcharts, dependency graphs, entity-relationship diagrams, and organization charts.

antvis/chart-visualization-skills · 253 tokens