agentsclimarketplace

Fetcher cosec auth

Skill Ahoo-Wang/skills/sources/fetcher/skills/fetcher-cosec-auth

A central aggregation repository for Agent Skills from Ahoo-Wang's open source projects.

Install
npx -y skills add Ahoo-Wang/skills --skill fetcher-cosec-auth

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when implementing CoSec authentication with Fetcher, including CoSecConfigurer, JWT token lifecycle, token storage, refresh handling, device ID storage, multi-tenant space resolution, resource attribution, authorization headers, and 401 or 403 error handling.

SKILL.md

2.0 KB, as published. Nobody here has run it

fetcher-cosec-auth

Use This Skill When

  • The task mentions CoSec, JWT, bearer auth, token refresh, or authorization headers.
  • The task needs device ID tracking, tenant or space resolution, resource attribution, or policy-aware requests.
  • The task involves 401 retry, unauthorized redirects, or forbidden error handling.
  • The task needs CoSec interceptors attached to a Fetcher instance.

Workflow

  1. Prefer CoSecConfigurer for app-level setup and use manual interceptors only for focused customization.
  2. Decide token storage, device storage, token refresher, and space provider before attaching interceptors.
  3. Register auth request/response interceptors only when refresh behavior is available.
  4. Keep 401 retry and 403 handling separate so auth recovery does not hide authorization failures.
  5. Load references/api.md for JWT classes, storage options, refresher contracts, headers, interceptors, and complete setup examples.

Key Practices

  • Treat tenant and owner attribution as request metadata, not hard-coded URL fragments.
  • Use cross-tab token storage behavior intentionally for multi-window apps.
  • Keep redirect/UI side effects in callbacks rather than inside low-level token classes.

References

  • references/api.md: Detailed package API, examples, and edge-case guidance. Load it only when the task needs CoSecConfigurer options, JWT token classes, TokenStorage, DeviceIdStorage, JwtTokenManager, TokenRefresher, CoSec headers, interceptors, space providers, and complete examples.

Related Skills

  • $fetcher-integration: Use for core Fetcher interceptor mechanics.
  • $fetcher-storage: Use for storage primitives behind token and device persistence.
  • $fetcher-react-hooks: Use for React security context and route guards.

Gives 0 of the 12 instructions most auth identity skills give

Counted across 409 of the 410 authors here whose files we hold, read 2026-08-06

  • hash passwords with bcrypt or argon2in 53 of 409, across 43 files
  • use parameterized queriesin 47 of 409, across 39 files
  • load SECRET_KEY from environment variablesin 23 of 409, across 14 files
  • validate all input server-sidein 19 of 409, across 11 files
  • refresh access tokens before expiryin 17 of 409, across 9 files
  • store tokens in httponly cookiesin 17 of 409, across 16 files
  • store refresh tokens securelyin 16 of 409, across 6 files
  • validate webhook signatures before processingin 15 of 409, across 5 files
  • sanitize user inputsin 15 of 409, across 9 files
  • implement rate limiting on auth endpointsin 14 of 409, across 9 files
  • encrypt sensitive data at restin 13 of 409, across 10 files
  • validate uploaded file extensions and sizesin 12 of 409, across 5 files

Said here and by no other author read

  • prefer CoSecConfigurer for app-level setup
  • decide storage and provider configuration before attaching interceptors
  • register interceptors only when refresh behavior exists
  • keep 401 retry and 403 handling separate
  • treat tenant and owner attribution as request metadata
  • use cross-tab token storage intentionally

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.