Credentials. AICSS_TOKEN is an account credential, so keep it in an environment variable or secret store and never commit it to the repository.
Who it is forA developer or team with an AICSS account who needs Pro components, which are not on npm, in a React, Vue, or Svelte project.
The problemPro components are not published on npm, so the team needs a token-based CLI path to get them into the codebase.
The outcomePro components are added to the project through @aicss/cli after the AICSS_TOKEN is set from the account page.
What you need first
- An existing React, Vue, or Svelte project
- npm and npx available in a terminal
- For Pro components only: an AICSS account and an AICSS_TOKEN from https://www.aicss.dev/account
Steps
- Get your token from your account at https://www.aicss.dev/account.
- Set the environment variable AICSS_TOKEN to that token in your shell or CI secret store.
- Run
npx @aicss/cli add thinking-statein the project root. - Open the added files and confirm the component imports and renders in the agent chat view.
Prompt for your agent
In the repo kvnkld/aicss, use @aicss/cli with the AICSS_TOKEN environment variable set to <token-from-env> to add the Pro component <component-name> to the project at <project-path>. Report the files created and confirm the token is not written into any project file.
Caveat. The README lists thinking-state as the example component and does not list which Pro components exist, so check your account page for what your token unlocks.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for kvnkld/aicss and "Add Pro thinking-state components with the CLI token"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer