# OKTA Agent Kit 0.5.3

Use the user's OKTA account through the existing CLI or hosted MCP. No separate
fal key or provider account is needed. Native model names, fields, limits and
prices come from the live OKTA schema and quote, not a static list in this kit.

## Install without a repository checkout

Extract the entire ZIP and enter `okta-agent-kit/`. Set `OKTA_API_KEY` securely in
the agent process environment; do not paste secrets into chat or commit them.

```sh
sh ./okta --json config test
sh ./okta --json skills list
sh ./okta --json skills show --id product-photoshoot
```

Windows equivalent: `.\okta.cmd --json config test`.
Direct executable: `node skills/okta-cli/scripts/okta-cli.mjs`.
Keep the adjacent config and reference files. Copy the complete desired folders
from `skills/` into your agent's supported skill directory, not isolated SKILL.md
files. The core CLI folder is required for local execution. Task skills may also
use an already configured OKTA MCP connection.

Eight skill entrypoints ship here: the core `okta-cli`, the native/media and
image-prompting guides, plus product photoshoot, social campaign, video
storyboard and thumbnail. Only load the task you need.
These are creative playbooks over existing capabilities, not new provider models.

## Shared execution

Discover with `fal models`, inspect `fal schema`, upload owned references, then
call `fal quote` with the exact input. Before the paid `fal submit`, keep the
user-approved budget and save a stable idempotency key. Measured H3 reference
quotes also need their returned quote ID. Use the same input/key on an ambiguous
submission; never purchase another job to recover a missing response.

`fal status` and `fal result` retrieve the same job. `fal result --output-dir`
saves every confirmed output into a NEW directory without overwriting. `--output`
saves only the primary output. `fal context` retrieves versioned inputs, ordered
stored output IDs, costs and the web URL for continuing in OKTA Chat. Hosted/local
MCP offers the same read-only context as `get_job_context`. An unfinished request
remains unfinished; don't invent
local paths or successful downloads. Native batch download is capped at 10 outputs
and 200 MiB per file. Failures preserve successful paths and report partial state.

## Distribution boundaries

Hosted MCP is available at https://okta.studio/api/mcp using the user's OKTA key.
A hosted server cannot read local paths. This ZIP also contains a bundled local
stdio MCP server (`server/stdio.mjs`) and portable `plugin.json`/`mcp.json` at
the ZIP root. Install the extracted `okta-agent-kit/` as a plugin or point an
MCP client at `node /ABSOLUTE/PATH/okta-agent-kit/server/stdio.mjs`. Configure
`OKTA_API_KEY` securely in that client process; no key is inside the ZIP. Set
`OKTA_WORKSPACE` only for a directory explicitly granted for local file access.
Local MCP uploads are capped at 4 MiB; this is not a large Direct-to-Storage
uploader. The bundle does not claim an npm release. Its included third-party
license texts are in `server/THIRD_PARTY_LICENSES.txt`.

`quote-price.mjs` now forwards exact native inputs to the live quote endpoint;
it does not guess from the old GPT Image 2 price snapshot. Old compact APIs remain
unchanged. For their continued use inspect their own model/settings contract.

Read https://okta.studio/docs/api for setup and API details. Version and per-file
SHA-256 values in MANIFEST.json identify this kit for support; checksums show
integrity within this archive, not an independent authenticity signature.